-
Notifications
You must be signed in to change notification settings - Fork 69
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
Error when using dynamic import -- support esnext
#54
Comments
Using Not sure what other effects would that have if I just changed it across the board for existing users. |
@ezolenko not actually working with this plugin |
Output here:
|
Yeah, the plugin overrides the module setting, so your If it works, I'll either switch to esnext (don't know what effect it will have on all other users) or expose module flag so it will actually go through. |
I didn't notice any downsides to using |
Why If I have a Whatever the override value is, the plugin should not override my config except it is allowed to. If I misunderstand anything here please correct me. |
@shunia before Now that there is more than one option, I'll have to relax the override (will probably take the value from tsconfig and warn if values is incompatible with rollup). |
One more question: But of course, if you have to implement this inside |
In worst case ( 0.12.0 is now on npm, that one will take tsconfig value, accepting |
esnext
What happens and why it is wrong
When using dynamic imports the following error is thrown:
This is caused by this module forcefully setting the
module
compiler option toes2015
.Environment
a.ts
b.ts
Versions
rollup.config.js
tsconfig.json
plugin output with verbosity 3
The text was updated successfully, but these errors were encountered: