5 ms·
Actually Webpack and Rollup go hand-in-hand. Rollup just compiles JavaScript ES6 modules into a single file, dealing with only `import` and `export` statements
by mrgalaxy 10y ago
Actually Webpack and Rollup go hand-in-hand. Rollup just compiles JavaScript ES6 modules into a single file, dealing with only `import` and `export` statements and some tree-shaking. Webpack handles everything else, like ES6-to-ES5 conversion, bundling dependencies, styles and everything else you need to get your code shippable to browsers and node.
- sergiotapia 10y ago>Actually Webpack and Rollup go hand-in-hand. Rollup just compiles JavaScript ES6 modules into a single file Isn't that webpacks gig. Or what that gulp? Or was that browserify? Or was that Jello? Or was that...
- draw_down 10y agoDoesn't seem so terrible to me for people to have a choice in what tool they use.
- nilliams 10y agoYou seem to be complaining that innovation is happening. If you don't want to deal with the inevitable 'options' that are going to be offered up by a community as large as the JS community, you could 1. pick a smaller community, 2. stick to old tech (e.g. at our company we still have an app running on RequireJS that runs just fine -- RequireJS is over 6 years old). 3. calmly re-assess tech choices every year or so.
- sergiotapia 10y ago>You seem to be complaining that innovation is happening. Not at all. I'm complaining that all of these seemingly similar tools keep superseding each other and solve...what exactly.
- nilliams 10y agoWhy do you think competitiveness of tooling is a bad thing? I understand why it could feel overwhelming, but you really can just pick one (assuming it appears to do what you want) and if it does, stick with it.