What's New in Webpack 2
gist.github.com
What's New in Webpack 2
1–10 of 71 posts
Re: What's New in Webpack 2
#2Huge. Between webpack and Babel, JS is quickly progressing towards becoming a powerful language that is easy to write, read and reason about. I'm currently in the process of moving an inherited "minified by hand" codebase to ES6, and the difference is incredible. Not only are linters catching hundreds of previously unknown edge cases and bugs, but the end result is more performant and smaller in file size. It's very satisfying, makes me not mind coding in JS again.
Re: What's New in Webpack 2
#3Huh, they've pulled es6 compilation in, away from babel?
It's early in the morning here so my pre-coffee brain might be terrible, but did they say which compilation engine they were using for es6?
Re: What's New in Webpack 2
#4Huge. Between webpack and Babel, JS is quickly progressing towards becoming a powerful language that is easy to write, read and reason about. I'm currently in the process of moving an inherited "minified by hand" codebase to ES6, and the difference is incredible. Not only are linters catching hundreds of previously unknown edge cases and bugs, but the end result is more performant and smaller in file size. It's very…
Have you looked into TypeScript? Type system helps you catch even more errors.
Re: What's New in Webpack 2
#5Huh, they've pulled es6 compilation in, away from babel? It's early in the morning here so my pre-coffee brain might be terrible, but did they say which compilation engine they were using for es6?
ES6 modules support are now baked into Webpack, which makes sense because that's supposed to be it's primary concern. Any other feature you'd still need to use Babel.
Re: What's New in Webpack 2
#6Huh, they've pulled es6 compilation in, away from babel? It's early in the morning here so my pre-coffee brain might be terrible, but did they say which compilation engine they were using for es6?
ES6 modules support are now baked into Webpack, which makes sense because that's supposed to be it's primary concern. Any other feature you'd still need to use Babel.
Yeah I saw that, I was more curious as to whether they had said anything about using a pre-existing compiler, or if they had built their own.
Re: What's New in Webpack 2
#7Is tree shaking still planned for this version?
Re: What's New in Webpack 2
#8has anyone used systemjs + jspm here ? I inherited a codebase using jspm (due to the override registry system that works great with legacy javascript packages - like Handsontabe) and am wondering about webpack.
Re: What's New in Webpack 2
#9Is tree shaking still planned for this version?
Yeah, it's in there.
Re: What's New in Webpack 2
#10What's the current thinking as of 2016 about Browserify versus Webpack? We've been happy Browserify users for a couple of years now, but I'm drawn to both the code splitting and dynamic expressions parts of Webpack.
On the other hand, I'm not keen on introducing more complexity or changing things just to be "fashionable", and Browserify, Babel, and Gulp do work together reasonably well for us (though I didn't much enjoy getting it all working in the first place, and I'm always nervous about updating any of them).