Support the "module" package.json field

[quantizor]

Similar to how there's an option to use "browser", it would be awesome to specify that Jest respect the "module" package.json field to resolve ES modules when using Babel with Jest.

[thymikee]

Are you interested in shipping a PR with this? :)

[quantizor]

Working on it right now :)

[thymikee]

Awesome 😎

[quantizor]

@thymikee would you mind reviewing that PR? I asked a few others but they seem to be busy.

[mrbinky3000]

Just wondering where we stand on this PR? Jest support for the "module" field would really help me out.

[quantizor]

I submitted a PR and it was ignored for a while, so I closed it.

[canercandan]

anyone can help unlock this freeze here? I am pretty much in the same situation than @probablyup and having this module parameter is very helpful for mono-repo based environment such as lerna

[loklaan]

@canercandan Had same case as you. Got around the issue by configuring Jest with a custom resolver that remaps module & main fields: https://gist.github.com/loklaan/9fe7768576466c5a31c2e7af4cfdecd0

Until the fields become configurable, this is the only (?) way to do what you need. You might need to write this resolver anyway, if you end up enabling watched-compilation for interdependent packages in your repo.

[canercandan]

@loklaan awesome thanks I will give it a try

[TehShrike]

@probablyup looks like the maintainers are still interested in merging if you want to re-open the pull request: #2704 (comment)

[quantizor]

I’m currently away but might have some time to reboot the PR this weekend. If someone else wants to grab it that’s fine too.