-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
paths
option
#754
Comments
Isn't rollup-plugin-alias the same? |
Not unless I've misunderstood rollup-plugin-alias – this is about external dependencies. (By extension, |
Rich-Harris
added a commit
that referenced
this issue
Jul 10, 2016
Merged
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Scenario: your bundle depends on an external library, but you don't want to do this sort of thing:
In the second case, you can end up in all sorts of contortions if the relative path from the bundle isn't the same as the relative path from the source file.
Proposed solution: use an external module ID, as normal, but then:
The text was updated successfully, but these errors were encountered: