Simen Bekkhus
Simen Bekkhus
AFAIK this is still relevant - can't remember merging anything that should affect it at least 🙂
There is #12536 fwiw
This sounds like a duplicate of https://github.com/facebook/jest/issues/12998#issuecomment-1212426850 - can you update `@jridgewell/trace-mapping` and see if that fixes it for you? If it does _not_, please open up a new issue...
> If it does _not_, please open up a new issue with a reproduction.
Then please open up a reproducing repo like the template asks you to. Your current steps don't. --- That said, it _is_ listed as a dependency within Jest: https://github.com/facebook/jest/blob/c8452412fa0e0f56955a3975aec996d4ec5b6702/packages/jest-transform/package.json#L20 All...
`node_modules` shouldn't have to be transpiled - unfortunately that seems to be the norm in RN. You probably need to adjust `transformIgnorePatterns`: https://jestjs.io/docs/configuration#transformignorepatterns-arraystring
No, but once we have `exports` I guess `imports` shouldn't be _too_ hard to build on top of it
Once a module implementing the algorithm exists (e.g. https://github.com/lukeed/resolve.exports/issues/14) we should be good to go for adding support here.
Plugging in a resolver should work fine, but it needs to support all cases. You could choose to e.g. look for `#` as first char and delegate (default resolver is...
Is it possible to get a reproduction without React where this is an issue? I think the underlying problem isn't jest doing something weird (we cannot inspect promise states, so...