-
-
Notifications
You must be signed in to change notification settings - Fork 30
ES6 support when using import instead of require #5
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
Comments
Are you already using the experimental ESM support in Node.js or are you transpiling your code? We should work just fine with transpiled code as that will just use But we will need to add support for native ESM at some point, but ESM support in Node.js is currently experimental and should not be used in production. In any case, it should be possible for us add support for ESM by using a custom loader: https://nodejs.org/api/esm.html#esm_loader_hooks |
Closing this for now due to lack of activity. Feel free to comment if you think it should be re-opened 🙂 |
Hello, is it something planned? Or maybe a way to force the detection? Thanks you, |
Hi @ebuildy, yes supporting ES modules is on radar. I'm not positive it would land in this module as the mechanism for hooking into |
+1 |
Hi,
Is there any way we can use this package to use for ES6's import syntax?
Thanks.
Regards,
Subhranshu
The text was updated successfully, but these errors were encountered: