Update nwb to the latest version 🚀 #27
Conversation
Version 0.23.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 37 commits.
There are 37 commits in total. See the full diff |
Update to this version instead 🚀 CommitsThe new version differs by 34 commits.
There are 34 commits in total. See the full diff |
|
|
|
|
|
|
🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚 Find out how to migrate to Snyk at greenkeeper.io
|
|
🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚 Find out how to migrate to Snyk at greenkeeper.io
|
|
🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚 Find out how to migrate to Snyk at greenkeeper.io
|
|
🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚 Find out how to migrate to Snyk at greenkeeper.io
|
|
🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚 Find out how to migrate to Snyk at greenkeeper.io
|
Version 0.22.0 of nwb was just published.
The version 0.22.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of nwb.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v0.22.0Breaking Changes
nwb.config.js, some of the nwb config you depended on may have changed, and the options Webpack accepts may have changed [#409]modeoption is now set to activate Webpack 4's new defaults, which removes the need for a bunch of manual configuration nwb was doing:ModuleConcatenationPluginis now automatically enabled inproductionmode instead of being explicitly configured, so nwb'swebpack.hoistingconfig has been removed.NamedModulesPluginis now automatically used indevelopmentmode instead of being explicitly configured.productionmode with minimization disabled, as the newdevelopmentmode defaults are unsuitable for code which will be published to npm.optimizationoptions are now used for certain pieces of configuration:optimization.noEmitOnErrorsis used instead ofNoEmitOnErrorsPluginto prevent emission of assets when using Hot Module Replacement.optimization.minimize/optimization.minimizerinstead of just addingUglifyJsPlugindirectly toplugins.CommonsChunkPluginhas been removed in Webpack 4 -optimization.runtimeChunkis now configured to create aruntimechunk (which replaces the oldmanifestchunk) andoptimization.splitChunksis configured to create avendorbundle.ExtractTextPluginwithMiniCssExtractPlugin:webpack.extractTextconfig withwebpack.extractCSSconfig - this is not backwards-compatible, as plugin options differ.performanceoption size warnings have been disabled (for now).nwb new inferno-appnow asks if you want to installinferno-compatas it's no longer a single dependency, defaulting to not installing it.nwb new preact-appnow asks if you want to installpreact-compat, defaulting to not installing it.webpack.compat.enzyme,webpack.compat.sinonandwebpack.style = 'old'config.Known Issues
.mjsfiles to npm, which is breakinginferno-*packages with Webpack 4, so e.g.inferno-compatwon't work if you want to reuse React components.Added
-f/--forceflag tonwb newto accept defaults and skip questions.Changed
index.htmlserving can now be configured with dot arguments - e.g. pass--fallback.disableDotRuleif you need to use dots in your path when using the HTML5 History API.--no-polyfillcan now be used to disable default polyfills for app projects as well as quick commands.Dependencies
url()sInternal
StatusPluginandInlineRuntimePluginto use the Use the new Webpack 4.hooksplugin API.Docs
publicPathdocs, as Webpack'soutput.publicPathconfig can't benull[#432] [stephenwf]Commits
The new version differs by 29 commits.
cbba39eRelease v0.22.0 as nwb@nextf0f9412Doc cleanupe4791d6Use a temporary scoped version of NpmInstallPlugin which supports Webpack 4245dbe9Allow dev server fallback serving to be configured with dot argumentsebdcae4Add --no-polyfill support to app commands6b7948dAdded inferno-* .mjs publishing to Known Issues6e271ebFixed webpack.debug - beautify is no longer a top-level option in UglifyJsPluginb741485Use createComponentVNode for exported components in the Inferno render shim5692966Update CHANGES for the uppgrade to Webpack 4 & dropping Node.js 4 supportc21d9e2Update lint confige3a91feUpdate uglify-webpack-plugin558e36bUse production mode for all UMD builds16849efUpgrade to Webpack 4a218457Re-disable inferno test75f51b9Update dependenciesThere are 29 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴