Simen Bekkhus

Since you mention transpilation; if you have a setup that transpiles `import` to `require` this issue is not the correct place - this issue is about native support. --- That...

>will that also allow for the Jest config file to be named jest.config.js? It can be named `.js` if its closest `package.json` has `type: 'module'`. Otherwise to use ESM in...

I think it makes sense to set those to `true` by default. Super breaking, but as long as we call it out in the blog post I think that's fine....

Could you put together a minimal repository showing the error?

This is almost certainly https://github.com/nodejs/node/issues/36351 or https://github.com/nodejs/node/issues/33439 (either way it's further upstream: https://bugs.chromium.org/p/v8/issues/detail?id=10284)

Again, this is a bug in V8, there is nothing we can do except wait for Google to fix and release it, then Node to update their version of V8...

cache is probably only shared within a worker/process, so using multiple workers doesn't have the same issue

PR welcome! > Here's a replay of the issue, for what it's worth [app.replay.io/recording/jest-shards-can-sometimes-have-0-tests-in-them--03c102a9-23de-4dff-9703-33c21e3103bc?point=649037107455789718243409532026952&time=1478.2236363636364&hasFrames=true](https://app.replay.io/recording/jest-shards-can-sometimes-have-0-tests-in-them--03c102a9-23de-4dff-9703-33c21e3103bc?point=649037107455789718243409532026952&time=1478.2236363636364&hasFrames=true) Super cool 😀

@rahul3002 are you still up for sending a PR? /cc @marionebl FYI

https://github.com/facebook/jest/releases/tag/v29.2.2