-
Notifications
You must be signed in to change notification settings - Fork 292
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
dynamic resolve fails #277
Comments
Would/does specifying |
I haven't tried that. In this case, I would need to deploy to Zeit the output of the ncc build run? My workaround was to pre-bundle the MJML package with NCC, publish it to npm, and import that in my app. This way I can just do |
Yes, thats how I understand it. Although I'm not sure it's possible, I think it may require a modification to the Thanks for letting me know about the workaround - I'll do the same for now! |
I've tested using externals and can confirm this appears to work
|
Since this is such a common problem, we've included this as the default behaviour in #307. |
Uglify JS (which is a dependency of another lib I'm using) uses this import format
This format fails with the
ncc run <filename>
command.Possibly a duplicate of #41
Here's a simple repo to demonstrate the issue : https://github.com/bfulop/zeitwithyarn
It fails with this error:
The text was updated successfully, but these errors were encountered: