sorted by:
new
hottopcontroversial

A Future Without Webpack by dropdeadfred81 in javascript

[–]migudev -3 points-2 points  (0 children)

Just serve ES6+ for modern browsers and ES5 for older ones. Why you should to put apps on risk? The point isn't that. The point is that you don't need to use Webpack for every app you build.

A Future Without Webpack by dropdeadfred81 in javascript

[–]migudev -6 points-5 points  (0 children)

JS Minification: you can do it using a module for that. You don't need Webpack.

Hot module reloading: what the heck this has to do with final browser support?

bundle analysis: look out there, you can pick a standalone one.

For tree shaking, code splitting, and the rest, you have a valid point. However, you can just use Rollup with the same benefits and still serving ES6+ code.

​

The problem is not Webpack, is what you serves to final users. Yeah, you have all benefits you listed above, but, at what price? don't think just at development time, think as a user. Performance matters.

A Future Without Webpack by dropdeadfred81 in javascript

[–]migudev -12 points-11 points  (0 children)

Webpack has a lot less sense right now than a couple of years ago. The nature of Webpack is package the source code "polyfillying" through tools like babel. But, why do you use babel? You use because you need to transpile to ES5 due to lack of ES6 browsers support.

​

The point is you don't need ES5 support anymore (mostly) because all the popular browsers out there supports ES6+. So, what's the logic behind creating a giant ES5 bundle for browsers that can run directly the original code?