-
-
Notifications
You must be signed in to change notification settings - Fork 263
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
Feature/support esm import remote #1469
Conversation
@ScriptedAlchemy - tested this change on "node-sync-bytedance" branch and confirmed nextjs still functioned normally |
🎉 This PR is included in version 8.1.0-canary.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 3.1.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 2.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 2.1.0-canary.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Support ESM via ImportRemote modules which is the default webpack output for NX. This is tricky due to TSC not supporting dynamic imports when module is type "commonjs"
microsoft/TypeScript#43329
@ScriptedAlchemy - if you are fine with this, I can add additional documentation to the Read Me. I tested this with a NX repo with output module on and off. The user would have to pass ESM which isn't ideal long term as we discussed but short term it gives them an option with the open NX issue.