Added:

Added a new web-app project type - this is for anyone who wants to use nwb's build/serve/test setup but isn't using React.
Added a --reload option to auto-reload the page when webpack hot module replacement gets stuck. This is primarily intended for use with the new web-app project type.
Command-line arguments can now be used to configure settings for nwb new.

Fixed:

Demo apps weren't generating sourcemaps when bundling.
Use a non-zero exit code when displaying usage or otherwise exiting due to missing arguments [#23]

Changed:

Commands which create files now log details of what they've created [#26]
The ES6 modules build for npm modules is now optional, controlled by a jsNext setting in nwb.config.js, defaulting to true.
- nwb 0.6 will default jsNext to true and log a warning when it's missing from a config file - this behaviour will be removed in nwb 0.7.

Dependencies:

copy-template-dir: v1.1.0 → v1.2.0 - provide created file paths in callback

0.5.0 / 2015-12-15

Added:

Top-level Webpack config can now be provided for loaders which support it, as a config object in their nwb.config.js loaders configuration. This is intended for loaders which can't use serialisable query config due to plugins, such as some CSS preprocessors [#18]

Fixed:

files config from template package.json was being used when packing nwb for publishing. Renamed them to _package.json to avoid this [#22]

Changed:

Downgraded qs dependency so nwb can be used with Node.js 0.12.x [#19]

Dependencies:

copy-template-dir: v1.0.5 → v1.1.0 - rename all files beginning with _
expect: v0.13.0 → v0.13.3 - Map, Set and circular comparison fixes
qs: v6.0.0 → v5.2.0 - downgrade to lose Node.js >= 4.0.0 requirement

0.4.1 / 2015-12-13

Fixed:

Bad npm package for 0.4.0 - npm was reading the new files config from package.json in templates for React components/web modules and applying it when packing nwb itself for publishing [#21]

0.4.0 / 2015-12-11

Added:

Added --fallback option to nwb serve, for serving the index page from any path when developing React apps which use the HTML5 History API [#16]
Added "engines": {"node": ">=4.0.0"} to package.json - nwb accidentally depends on this because it uses qs v6 [#19]
Added files config to React component/web module package.json templates.
- The files config for the React component template assumes that components published to npm with require() calls for CSS which ships with it will use a css/ dir.
Added a default ES6 build with untranspiled ES6 module usage [#15]
- This is pointed to by jsnext:main in project template package.json for use by tree-shaking ES6 bundlers.

Fixed:

Added missing main config to React component/web module package.json templates, pointing at the ES5 build in lib/.
Express middleware wasn't included in npm package.

Changed:

1.0.0 is now the default version for template projects.

0.3.1 / 2015-12-09

Fixed:

Generic nwb build was broken for React components/web modules in 0.3.0.

0.3.0 / 2015-12-07

Added:

Support for CSS preprocessor plugin packages [#6]
- Loading of configuration objects exported by 'nwb-*' dependencies found in package.json.
- Creation of style loading pipelines for plugins which provide cssPreprocessors configuration.
  - nwb-less
  - nwb-sass

Fixed:

Babel config is now passed to Babel when transpiling modules [#13]

0.2.0 / 2015-12-05

Added:

Express middleware for running a React app on your own development server using nwb's Webpack config generation [#8]

Changed:

Webpack loader config objects are now merged with webpack-merge; query objects will now be deep merged, with lists occurring at the same position in build and user config being concatenated instead of overwritten.

Fixed:

babel-runtime can now be resolved from nwb's dependencies when using optional: ['runtime'] Babel config [#10]
Paths to resources required from CSS in React app builds [#9]

0.1.0 / 2015-12-02

First 0.x release.