-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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 builds are unusable in NodeJS #6127
Comments
@vladfrangu Thanks for testing RC, this issue is fixed under #6032 and another RC with fix will be released in this week. |
Awesome! Just one curiosity, does that also fix the missing |
@vladfrangu what does the error output look like for missing .js extensions? |
See the first error sent in the issue report! |
For
there will still need of |
Ideally tho that shouldn't be needed! Not only because its experimental (so we don't know if it'll even remain in node, although it's likely it will remain), but because the fix is quite simple (which is just appending |
Thanks @vladfrangu i'll be taking a look into getting rid of the experimental flag and seeing if I can get this out before release, if not it'll be apart of the next update. |
@vladfrangu thank you so much for creating this issue and even providing me an idea on how to do it :) created a PR and hopefully will be merged soon after feedback. |
Thanks @luu-alex |
Expected behavior
Importing the module in an ESM-based project should not throw errors
Actual behavior
Importing the module in an ESM-based project throws errors related to missing file extensions.
Running node with
--experimental-specifier-resolution=node
throws a separate error related to lack of import assertions on JSON files.Steps to reproduce the behavior
web3@4.0.1-rc.1
test.mjs
)Environment
The text was updated successfully, but these errors were encountered: