-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Rollup build proof of concept #3429
Conversation
@outofambit Have you tried a Parcel setup? From what I see here it seems that it's including several additional plugins to be able to build what we want. I had a quick try with Parcel simply running I think Parcel is pretty promising in this sense as I did not have to do any additional thing at all, no plugins no configs and it already minifies and includes json. Not sure if anything else is needed though. |
@limzykenneth I haven’t tried Parcel yet, but that sounds promising! I was also disappointed in the number of plugins needed for pretty basic functionality in rollup. (From reading issues in rollup’s repo, there’s a lot of discussion around this.) When I have some more time I’ll put up another test branch with parcel 🙂 |
I also found https://github.com/developit/microbundle, a wrapper for rollup that looks much simpler. Might be worth also trying out. |
closing this in favor of continuing exploration in #3431 🚀 |
Did a quick proof of concept on replacing browserify with rollup to aid discussion in #3425. This is here mostly to have a convenient place for others to see the diff. :)
I only touched
browserify.js
(and notcombineModules.js
), so I couldn't remove any npm dependencies. However I was able to remove the need forderequire
anduglify
in the build, so they could be removed (frompackage.json
andGruntfile.js
) ifcombineModules.js
is also ported to use rollup.If you want to try it out locally, checkout this branch and then:
😄