21–30 of 59 posts
Now that Webpack has tree shaking, are there still reasons to use Rollup?
That is just one situation though.
Now that Webpack has tree shaking, are there still reasons to use Rollup?
However Rollup currently lacks a lot of features that make Webpack a good choice for large and complex apps.
You can get a feel for the code Rollup generates at http://rollupjs.org.
Semi-related: I also found it useful to name the config file webpack.config.babel.js instead of webpack.config.js so I can use ES6 in my Webpack config.
Webpack 2 is so awesome that I'm really confused why haven't they released it as a non-beta yet. It's way past MVP and has more than enough quality for a non-beta. It looks like the maintainers want it to get perfect and release it "when it's done", and that is so wrong.
We are just around 90% completion (http://github.com/webpack/webpack.js.org/milestone/1)
After that we will release v2. Help always wanted! <3
What is the difference from Webpack 1? This tutorial seems identical to every other Webpack getting started I've read.
There's a list from the start of the year here: https://gist.github.com/sokra/27b24881210b56bbaff7
What is the difference from Webpack 1? This tutorial seems identical to every other Webpack getting started I've read.
There's a list from the start of the year here: https://gist.github.com/sokra/27b24881210b56bbaff7
Now that Webpack has tree shaking, are there still reasons to use Rollup?
Rollup's gains come mainly from the way it combines modules into a single scope, rather than wrapping them in functions and shipping a module loader with the bundle. It's not uncommon to see parse/evaluate time plummet when switching to Rollup because of this, which is often more important than the number of bytes. However Rollup currently lacks a lot of features that make Webpack a good choice for large and complex…
Now that Webpack has tree shaking, are there still reasons to use Rollup?