As I've been working towards splitting the first book, I realized I must do one more release of this webpack one before I can complete it. That's what the current release, 1.2.0, is about. I've moved certain content there (mainly linting, npm related) and done assorted tweaks based on feedback.
Compared to the previous release we have something more mature together now. There are still improvements in store, but you have to take one step at a time.
Getting the split done successfully is my next major goal with this effort. Completing that will take a lot of pressure out of my shoulders and allow new content to be developed more easily.
Speaking of new content, I produced a set of React training slides for a session. A lot of the research done for the slides will fold back to the written content eventually. Even though it took a lot of time and effort to produce the set, I believe it was worth it.
In addition to pushing the book content further, I spent some time contributing to webpack-validator. The tool is growing nicely. There's still a lot to do, but it's progressing nicely. The biggest advantage of having this kind of shell around webpack is that it is able to catch issues early while saving your valuable time.
The development of the training slides took serious effort, but fortunately now that's done, I don't have to worry about slides so much anymore should I get training requests. The initial set can be developed further and perhaps turned into something greater, but more on this later.
My next goal is to finish the split. There is still some content to be developed and infrastructure work to be done, but it's gladly it's not that far away! Most importantly Leanpub has completed its share so now I just need to finish my part and we are in a good place with this.
1.2.0#In total 36 commits went to the book since the last release. You can find the important changes below. See GitHub for all changes. Remember especially the "Files changed" tab as it gives you a good overview of what's happening with the book.
path.join and other path related portions to a platform agnostic format. This is to avoid issues on Windows. Slashes tend to be problematic. Thanks Viktor!webpack --watch. That provides a nice bridge to the HMR topic and it's one of those features you might want to be aware of in case you don't want to use webpack-dev-server for some reason and are just interested in generating a build automatically.vendor: Object.keys(pkg.dependencies) over vendor: Object.keys(pkg). That was the original intention after all. Thanks Viktor!console statements from your source. Uglify works too, but this is a good alternative to be aware of especially if you use Babel already.paths and additional options should be a little clearer. Thanks Christian!output.publicPath field. That is useful to be aware of as you can use it to manipulate your asset paths and point to a CDN for instance.externals. I don't use it myself, but I felt it was worth mentioning about.webpack.NoErrorsPlugin() can be potentially useful with HMR. It allows you to see possible syntax errors at the console over the error overlay used by the hmre preset.Even though this isn't a huge release, it's a solid step towards something nicer. As usual, the content will evolve as more experience is gained. I find it particularly cool that a little effort like this can help to motivate improvements in tooling as well.
As stated earlier, my next goal is to finish the split. It's good to have this side of the fence in a good shape so we can get the other part across it as well. If you bought the original React/Webpack book, you'll get access to the digital version of this one then. The pricing model will change then (total value goes up) as I like to thank my early supporters.
Of course if you want to support the development of the book, pick up a copy at Leanpub. You can still gift the coupon to a friend. A part of the income (around ~30%) goes to Tobias Koppers, the author of webpack. This is my way of supporting his work given mine builds on top of his.