Jest cannot find module react-dom about use-context-selector

[dai-shi]

Thanks for reporting.
If umd.js is an issue, can you try the resolver?
https://jestjs.io/docs/configuration#resolver-string

By combining defaultResolver and packageFilter we can implement a package.json "pre-processor" that allows us to change how the default resolver will resolve modules. For example, imagine we want to use the field "module" if it is present, otherwise fallback to "main":

...but, that's just a workaround. I wonder how we could solve this without such a workaround. help wanted. (this issue is probably not only with use-context-selector but with all my other packages with microbundle.)

[gsevla]

It worked!

Thanks for the answer.

I readed about the problem, but have no ideas to solve it, sorry (have no expertise with bundlers)

[dai-shi]

Good to hear that.

No problem. Let's leave this issue open for a while in case someone jumps in.

[BrunoADPaixao]

Thanks for reporting. If umd.js is an issue, can you try the resolver? https://jestjs.io/docs/configuration#resolver-string

By combining defaultResolver and packageFilter we can implement a package.json "pre-processor" that allows us to change how the default resolver will resolve modules. For example, imagine we want to use the field "module" if it is present, otherwise fallback to "main":

...but, that's just a workaround. I wonder how we could solve this without such a workaround. help wanted. (this issue is probably not only with use-context-selector but with all my other packages with microbundle.)

I'm having the same error. Using this solution now a have the same error but with the index.modern.js. Any sugestion?

[dai-shi]

So, is this the problem with RN + jest? It works with RN only and maybe React (web) + jest, doesn't it?

[mtroskot]

@gsevla can you post the workaround steps how to fix the issue?