Joe Pea
Joe Pea
new issue: https://github.com/vercel/serve-handler/issues/178
I am able to work around the issue for now by adding this to `web-test-runner.config.js`: ``` concurrency: 1 ``` which works, but not as quickly.
Hmmm, I'm investigating that piece of code, and sometimes I can't reproduce the problem at all (f.e. 100 runs work fine). But then sometimes, it fails right away. So I'm...
A workaround to this is probably to install fake timers with sinon. I haven't tried it yet. Using fake timers has allowed writing deterministic tests that don't fail due timing...
I'm trying to debug, and to me it seems that puppeteer promises for exposed functions are not resolving inside the browser context. I changed ChromeLauncherPage.ts to the following to try...
The downside of adding this to web-test-runner is: - more maintenance for maintainers - more surface area for things to go wrong Plus, as a user, you have more control...
I think we should limit scope, and not let those issues stop something that is great for most people (already proven by Lerna, Yarn, Pnpm, and others). We can limit...
> I'd also like to point a related (and very recent RRFC, ref: #706) that sounds to me a little more actionable at tackling the running-multiple-interdependent-scripts-in-a-project challenge. Upon taking a...
Script coordination and locking does not need to be a feature of NPM in order to ship a feature like wireit that makes script ordering super simple to manage. Lerna...
I can't switch to npm workspaces for script running. A feature like this would be huge for NPM!