v0.6.0
Added:
- Added an
nwb init
command - same asnwb new
but creates a project in the current directory and uses the directory name by default [#25] - 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 [#24] - Added a
--reload
option to auto-reload the page when webpack hot module replacement gets stuck. This is primarily intended for use with the newweb-app
project type. - Command-line arguments can now be used to configure settings for
nwb new
.
Fixed:
- Production optimisations weren't being applied to React app builds.
- 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:
- Reorganised and coloured
nwb help
output. - 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 innwb.config.js
, defaulting totrue
[#27]- nwb 0.6 will default
jsNext
totrue
and log a warning when it's missing from a config file - this behaviour will be removed in nwb 0.7.
- nwb 0.6 will default
Dependencies:
- copy-template-dir: v1.1.0 → v1.2.0 - provide created file paths in callback
- css-loader: v0.23.0 → v0.23.1
- expect: v1.13.3 → v1.13.4 - comparing arrays of nested objects fix
- rimraf: v2.4.4 → v2.4.5
New help output screenshots on Windows and Linux: