Release: Starter Kit Legacy

This release maps to version v0.1.0 and is the last release of Starter Kit to include Gulp.

If you're needing the old Gulp-based workflow for whatever reason, this is the version you want to use. The legacy tag will always be updated to the most recent legacy version of Starter Kit.

Bugfix release v1.0.1

This small new release fixes a few sundry issues since "Webpackify" (v1.0.0):

• Fixes images not revving, being usable locally (issues #139, #138; fixed by #140)
• Replaces nunjucks-webpack-plugin with nunjucks-html-loader to enable live-reloading (issue #135, fixed by #137)

Release: Webpackify

This is a new release that totally redoes the build process and (hopefully) works substantially better than the Gulp-based workflow we used previously. I'm tagging it as v1.0.0 as we need to start using semantic versioning to communicate the Starter Kit and have not used versions at all previously. The previous Gulp-based version is still available using the tag legacy, which maps to the newly-created v0.1.0 version.

On a whole, however, this release has been built with backwards interoperability in mind so if you don't dig into the internals of Starter Kit you probably won't notice much of a difference (Beyond that it's faster and more reliable).

Differences between "Old Starter Kit" and "New Starter Kit"

• The main development server port is now 8080 instead of 8000. Open http://localhost:8080 instead.
• You now must import your entry CSS file into index.js:

import './styles.scss';

This is because Webpack builds and bundles your styles with your main code bundle as part of the build process, then extracts them into a separate CSS file afterwards.

This is done for you during scaffolding, but it's good to be aware of it.

• The main built files in dist/ are now called bundle.js and bundle.css.
• Images are now minified by default, without any extra configuration (See #119), and are meant to be added in the client/images directory.
• PostCSS is now used with style compilation. Feel free to experiment with adding new plugins!
• All build process configuration now takes place in webpack.config.js. Gulp is gone, don't look for a Gulpfile any more!

Known issues

• The Nunjucks Webpack plugin used works well but still lacks functionality and is poorly supported compared to html-webpack-plugin (the standard for generating HTML files from templates in Webpack). At some point it may be prudent to replace it.
• Code-splitting should be added to improve web performance.
• The default bundle size is already excessively big; I (@Aendrew) will be investigating how to improve that.
• Error logging from Nunjucks templates could probably be improved.