Getting Started with Webpack 2
blog.madewithenvy.com
Getting Started with Webpack 2
1–10 of 59 posts
Re: Getting Started with Webpack 2
#2What is the difference from Webpack 1? This tutorial seems identical to every other Webpack getting started I've read.
Re: Getting Started with Webpack 2
#3What is the difference from Webpack 1? This tutorial seems identical to every other Webpack getting started I've read.
I guess most of the changes are 'under the hood', but there are some breaking changes in configuration as well.
"loaders" => "rules" etc.
http://javascriptplayground.com/blog/2016/10/moving-to-webpa...
Re: Getting Started with Webpack 2
#4Interestingly, things seem to be settling down in the JS community. In the past, every time a library lacked a particular feature, the community suddenly abandoned it. At the same time, every new version release had all sorts of horrible breaking changes, that made upgrading a very scary task.
Now, the JS community seems to be thinking more about stability and backwards compatibility. That's very welcome, at least from the perspective of this grumpy server-side developer.
Re: Getting Started with Webpack 2
#5What 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:
Re: Getting Started with Webpack 2
#61 point of minor interest is that they start by using Yarn, not NPM. Little things like that (esp from a major project like Webpack) can develop into definite trends.
Re: Getting Started with Webpack 2
#7What is the difference from Webpack 1? This tutorial seems identical to every other Webpack getting started I've read.
I think the biggest addition is ES2015 modules.
Webpack now understands them without the need to convert them to commonjs/amd.
import works statically (before the JS is run), which allows webpack to make some optimizations.
(System.import() is used for dynamic (runtime) imports)
Re: Getting Started with Webpack 2
#8Semi-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.
Re: Getting Started with Webpack 2
#9I currently use gulp and, over the yars, have found many ways to do my own parsing and smart caching and stuff over, like checking and bumping version numbers, conditional compiling, caching assets etc.
I'd hate to loose all that, but I do see the advantages of Webpack. How much control do I have with Webpack though? Can I still write my own hooks?
Re: Getting Started with Webpack 2
#10Now that Webpack has tree shaking, are there still reasons to use Rollup?