A toolkit for React, Preact, Inferno & vanilla JS apps, React libraries and other npm modules for the web, with no configuration (until you need it)
Node.js 6 is no longer supported; Node.js 8.9.0 is now the minimum required version, as per many of nwb's dependencies.
Updated to Babel 7
babel.runtime config no longer accepts a String to enable an additional, named feature.
Pass an Object with plugin options instead.
Support for tests in *-test.js files has been removed, as @babel-core no longer supports pattern matching them to ignore them when co-located in src/.
Rename these to *.test.js instead.
Dropped support for the old --no-hmre alias to disable Hot Module Replacement, just use --no-hmr instead.
Updated Preact config for Preact X.
Dependencies with (documented) breaking changes:
babel.proposals config to configure use of Babel's proposal plugins.en property to webpack.html config to set the document language when using nwb's default HTML template [#520] [Muhnad]UglifyJsPlugin with TerserWebpackPlugin.preact/compat is now part of the preact module.Deprecated babel.stage config, as Babel's stage-X presets were/are being removed in Babel 7 - if you provide it, nwb will warn you and enable Babel proposal plugins equivalent to the current stage they're at.
Use babel.proposals config instead if you want to toggle some or all additional proposal plugins on.
Deprecated webpack.uglify config, which has been renamed to webpack.terser.
Autoprefixer renamed its browsers option to overrideBrowserslist, so you will get deprecation warnings if you were using {browsers: ...} in webpack.autoprefixer config.
inferno-* packages (such as inferno-compat) work again with Webpack 4 [#440]prepublishOnly to react-component and web-module project package.json scripts, which invokes npm run build prior to publishing [#436] [hanford]npm.umd.entry config to specify a different entry point for the UMD build in npm module projects. Currently, the UMD build requires an entry point which must have a default export [#411]CopyPlugin when webpack.copy config is provided [#431]nwb.config.js, some of the nwb config you depended on may have changed, and the options Webpack accepts may have changed [#409]
mode option is now set to activate Webpack 4's new defaults, which removes the need for a bunch of manual configuration nwb was doing:
ModuleConcatenationPlugin is now automatically enabled in production mode instead of being explicitly configured, so nwb's webpack.hoisting config has been removed.NamedModulesPlugin is now automatically used in development mode instead of being explicitly configured.production mode with minimization disabled, as the new development mode defaults are unsuitable for code which will be published to npm.optimization options are now used for certain pieces of configuration:
optimization.noEmitOnErrors is used instead of NoEmitOnErrorsPlugin to prevent emission of assets when using Hot Module Replacement.optimization.minimize/optimization.minimizer instead of just adding UglifyJsPlugin directly to plugins.CommonsChunkPlugin has been removed in Webpack 4 - optimization.runtimeChunk is now configured to create a runtime chunk (which replaces the old manifest chunk) and optimization.splitChunks is configured to create a vendor bundle.ExtractTextPlugin with MiniCssExtractPlugin:
webpack.extractText config with webpack.extractCSS config - this is not backwards-compatible, as plugin options differ.performance option size warnings have been disabled (for now).nwb new inferno-app now asks if you want to install inferno-compat as it's no longer a single dependency, defaulting to not installing it.nwb new preact-app now asks if you want to install preact-compat, defaulting to not installing it.webpack.compat.enzyme, webpack.compat.sinon and webpack.style = 'old' config..mjs files to npm, which is breaking inferno-* packages with Webpack 4, so e.g. inferno-compat won't work if you want to reuse React components.-f/--force flag to nwb new to accept defaults and skip questions.index.html serving can now be configured with dot arguments - e.g. pass --fallback.disableDotRule if you need to use dots in your path when using the HTML5 History API.--no-polyfill can now be used to disable default polyfills for app projects as well as quick commands.url()sStatusPlugin and InlineRuntimePlugin to use the Use the new Webpack 4 .hooks plugin API.publicPath docs, as Webpack's output.publicPath config can't be null [#432] [stephenwf]nwb.config.js files has been expanded, so previously valid config files may now be invalid [#136]
babel, karma, npm and webpack configuration (i.e. anything that's not documented in the Configuration docs) are now treated as errors [#193]nwb check-config to check your configuration file.webpack.uglify config you have against the new version's options documentation - options for UglifyJS itself must now be passed as an uglifyOptions object and some of UglifyJS' default options have changed.engines config of nwb's dependencies.nwb.config.js Config Changeswebpack.compat.sinon flag for Sinon 1.x compatibility settings, as subsequent major versions since July 2017 support Webpack out of the box.--open flag to open the app in your default browser or in a named browser (e.g. --open="Google Chrome") after starting a Webpack dev server [#334]babel.config() function which will be given the generated Babel config to do whatever it wants with.karma.config() function which will be given the generated Karma config to do whatever it wants with [#408]webpack.compat config
webpack.copy config
--copy-files for component builds more visible [#407]default export of the entry point, rather than an ES modules interop object which looks something like {__esModule: true, default: Getter}, which was unintended behaviour. This will break any existing usage of UMD builds which depended on manually accessing the unintended default property [#402]16.x - fixes creating components with npm 2.--unsafe-perm workaround for PhantomJS' postinstall step failing on some OSes when installing globally with npm 5 [#383]