-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ESM compabillity #70
Comments
This seems like it's still an issue. We've updated our project to use ESMs and experience the same error message. I thought that the 2.0 release would be enough. Is this related to jestjs/jest#11677? |
Not related. I'll take a look. |
It's the ways typescript exports in newer versions. for esm the export must be enumerable i think. Thats the only difference i've seen in the version diff. |
Can you test out version |
@marchaos At least for me this doesn't change a thing:
|
Same issue here. Any suggestion on how to resolve it? |
For anyone with the same issue, I've been unable to work out how to use the |
Maybe the cause if that
I'll give it a try and open a pull request if it's fix the issue. |
I have opened a pull request that should solve the issue. Note that jest-resolve actually doesn't support hybrid package.json (ESM + CJS) as node Conditional exports properties are NOT read here : For extension-less imports (like dependencies), it only checks for So, when importing |
Since 1.0.17 or 1.0.18 this package no longer works with jest in esm mode.
I think it's because of the new different typescript compilation.
The text was updated successfully, but these errors were encountered: