Simen Bekkhus
Simen Bekkhus
I don't understand what this does. Which issue does it solve?
> any tips for how I might pass that V8 flag down through all the workers? I would have thought https://github.com/facebook/jest/blob/e0b33b74b5afd738edc183858b5c34053cfc26dd/packages/jest-worker/src/workers/ChildProcessWorker.ts#L93-L94 made it so it was passed down...
If it's specifically in 16.11, you can probably try to build node yourself and bisect https://github.com/nodejs/node/compare/v16.10.0..v16.11.0. Figuring out which commit that introduced it might help understand when one (or more)...
PR very much welcome! I'm surprised it doesn't work already 😅
@orta talked about this when we met up in March, and I think it's mostly in his head beyond the sketches he shared with you. I don't _think_ we have...
nothing wrong with it, and I guess we could use it instead of code sandbox. This issue is about a version of jest running natively in the browser, though, and...
1. I don't know. Maybe @amasad could help us? It'd be great to upgrade to Jest 24 as well 2. Docusaurus 2 should support client side scripts, so we can...
Most definitely still want this (like react beta docs have)
Yeah, this won't work as the types packages _are_ dependencies (i.e. pur types aren't consumable without them being installed)
First comments is that the setupfiles shouldn't assign to `this`. If we do this, I think the setup should `return` something, and we can assign that inside of jest itself...