All Versions
90
Latest Version
Avg Release Cycle
45 days
Latest Release
1408 days ago

Changelog History
Page 9

  • v0.6.2 Changes

    December 30, 2015

    Dependencies:

    • ๐Ÿš€ argv-set-env: v1.0.0 โ†’ v1.0.1 - docs
    • โช glob: v6.0.1 โ†’ v6.0.3 - v6.0.2 was reverted
    • ๐Ÿš€ karma: v0.13.15 โ†’ v0.13.16
    • karma-mocha-reporter: v1.1.3 โ†’ v1.1.4 - handle duplicate descriptions
    • karma-phantomjs-launcher: v0.2.1 โ†’ v0.2.2
    • ๐Ÿš€ react-transform-catch-errors: v1.0.0 โ†’ v1.0.1 - display the offending call stack more prominently
    • rimraf: v2.4.5 โ†’ v2.5.0 - add glob option
    • ๐Ÿ”€ webpack-merge: v0.3.2 โ†’ v0.5.1 - fix recursive merging
  • v0.6.1 Changes

    December 30, 2015

    ๐Ÿ›  Fixed:

    • 0๏ธโƒฃ The es6/ directory wasn't included in the default .gitignore for npm module project skeletons.
  • v0.6.0 Changes

    December 23, 2015

    โž• Added:

    • โž• Added an nwb init command - same as nwb 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 new web-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 in nwb.config.js, defaulting to true [#27]
      • 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 v0.7.

    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
  • v0.5.0 Changes

    December 15, 2015

    โž• 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: v1.13.0 โ†’ v1.13.3 - Map, Set and circular comparison fixes
    • โฌ‡๏ธ qs: v6.0.0 โ†’ v5.2.0 - downgrade to lose Node.js >= 4.0.0 requirement
  • v0.4.1 Changes

    December 13, 2015

    ๐Ÿ›  Fixed:

    • ๐Ÿ“ฆ Bad npm package for 0.4.0 - npm was reading the new files config from package.json in templates for React component/web module skeletons and applying it when packing nwb itself for publishing [#21]
  • v0.4.0 Changes

    December 11, 2015

    โž• 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 skeleton package.json.
      • The files config for the React component skeleton 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 skeleton package.json for use by tree-shaking ES6 bundlers.

    ๐Ÿ›  Fixed:

    • โž• Added missing main config to React component/web module skeleton package.json, pointing at the ES5 build in lib/.
    • ๐Ÿ“ฆ Express middleware wasn't included in npm package.

    ๐Ÿ”„ Changed:

    • 0๏ธโƒฃ 1.0.0 is now the default version for project skeletons.
  • v0.3.1 Changes

    December 09, 2015

    ๐Ÿ›  Fixed:

    • ๐Ÿ— Generic nwb build was broken for React components/web modules in 0.3.0.
  • v0.3.0 Changes

    December 07, 2015

    โž• 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]
  • v0.2.0 Changes

    December 05, 2015

    โž• 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]
  • v0.1.0 Changes

    December 02, 2015

    ๐Ÿš€ First 0.x release.