-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
feat: esm format #12
Labels
Comments
🎉 This issue has been resolved in version 2.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Amazing, thank you @egoist |
Any idea about this one?
I got a few errors like this (can provide repro if needed). I seem to hit evanw/esbuild#566 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, when importing native ESM packages (
"type": "module"
), I get the following error:I believe this is happening because esbuild is converting the esm import to cjs requires.
Seems like there's an overrides option to pass in
format: 'esm'
here, but I'm guessing this is only available for the Node.js API.Can esbuild-register pass in
format: 'esm'
to esbuild if a flag is set or if the current projectpackage.json
hastype: 'module'
set?The text was updated successfully, but these errors were encountered: