Use Rollup instead of Webpack - #3019
Closed
fregante wants to merge 1 commit into
Closed
Conversation
Member
Author
|
Related: Parcel PR #2983 |
4 tasks
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Our Webpack config is huge and the output is ugly (and not optimized: webpack/webpack#10720), so I've been looking at alternatives.
Sadly Rollup is too slow (rollup/rollup#3506) and it requires extra code/config to match Webpack-as-an-app-builder capabilities (e.g. copying asset files effortlessly).
This is always the problem. Rollup output is always 💯 but it's limited/limiting.
This can be revisited once there's a way to parallelize the build and sync assets effortlessly.