The version 0.19.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of nwb.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notesv0.19.0
0.19.0 / 2017-10-02
Breaking Changes
Removed hooking of React, Preact and Inferno render() functions in quick commands, as this won't work with ES modules builds (which are used by default in Webpack v3). This affected the current version of Preact at the time of writing.
If you're manually using render() with quick commands, you must now handle providing the target DOM node too - document.getElementById('app') is available in the default HTML template.
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 0.19.0 of nwb just got published.
The version 0.19.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of nwb. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
v0.19.00.19.0 / 2017-10-02
Breaking Changes
render()functions in quick commands, as this won't work with ES modules builds (which are used by default in Webpack v3). This affected the current version of Preact at the time of writing.render()with quick commands, you must now handle providing the target DOM node too -document.getElementById('app')is available in the default HTML template.Added
babel.envconfig to pass additional options forbabel-preset-env.webpack.compatfor recent versions of React 15.Changed
babel-preset-envinstead of deprecatedbabel-preset-es201Xpresets [#375]beautify: trueforwebpack.debugoutput so code split bundles are readable.Dependencies
React.PureComponentto the list of default super classesCommits
The new version differs by 23 commits.
c04b2f4Release v0.19.0b56d36dUpdate dependencies19bd6baUpdate dependencies47b9d74Update dependencies5172ccdAdded additional Enzyme compat config for recent versions of React 15d0ff1deUpdate dependencies9a838a6Update dependenciesddbd30fFix CLI help alignment67a873cMerge pull request #377 from jamrizzi/jamrizzi/cli-doc-error8842ad9Update dependenciesc32f892Use babel-preset-env instead of deprecated babel-preset-es201X plugins2bd49e5Update dependencies4cb447aRevert "Revert use of preact/debug in favour of preact/devtools"159c62eCLI help documentation error4257d54Update babel-runtimeThere are 23 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: