The version 1.0.11 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 react-scripts.
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 Notesv1.0.11
1.0.11 (2017-08-09)
🐛 Bug Fix
create-react-app
#2884 Improve offline heuristic for proxied environments. (@bsyk)
When a Yarn proxy is set, we will check its connectivity if we cannot reach Yarn's registry. This is often the case when DNS lookups must be made through the proxy.
#2853 Allow use of scoped packages with a pinned version. (@wileybenet)
react-dev-utils
#2796 Properly escape HTML tags in error overlay. (@ccloli)
Elements printed in their entirety would sometimes render as HTML. This should no longer happen and should properly render as text.
react-dev-utils, react-scripts
#2834 Make formatWebpackMessages return all messages (@onigoetz)
As applications grow more complex, it is possible webpack may run out of memory while generating source maps. They may now be disabled by setting GENERATE_SOURCEMAP=false.
#2913 Allow flags to be passed to node when running react-scripts. (@koistya)
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 1.0.11 of react-scripts just got published.
The version 1.0.11 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 react-scripts. 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
v1.0.111.0.11 (2017-08-09)
create-react-app#2884 Improve offline heuristic for proxied environments. (@bsyk)
When a Yarn proxy is set, we will check its connectivity if we cannot reach Yarn's registry. This is often the case when DNS lookups must be made through the proxy.
#2853 Allow use of scoped packages with a pinned version. (@wileybenet)
react-dev-utils#2796 Properly escape HTML tags in error overlay. (@ccloli)
Elements printed in their entirety would sometimes render as HTML. This should no longer happen and should properly render as text.
react-dev-utils,react-scriptsformatWebpackMessagesreturn all messages (@onigoetz)react-scriptsnodefile resolution. (@mostafah)react-scripts#2818 Allow sourcemaps to be disabled. (@viankakrisna)
As applications grow more complex, it is possible webpack may run out of memory while generating source maps. They may now be disabled by setting
GENERATE_SOURCEMAP=false.#2913 Allow flags to be passed to node when running
react-scripts. (@koistya)#2574 Upgrade to
webpack@3. (@themre)#2747 Simplify webpack configuration using
Rule.oneOf. (@Furizaa)react-dev-utils,react-scriptspackage.json. (@iamdoron)create-react-appreact-dev-utilslaunchEditor. (@danrr)launchEditorso--remoteworks. (@trygveaa)eslint-config-react-app,react-scriptseslint@4. (@trungdq88)eslint-config-react-appallowTaggedTemplatesto true (eslint). (@denkristoffer)react-dev-utilswebpackHotDevClientsupport. (@ForbesLindesay)react-scriptsbasenamefeature inreact-router. (@viankakrisna)source-map-explorer. (@hodanny)babel-preset-react-appcreate-react-app,eslint-config-react-app,react-dev-utils,react-error-overlay,react-scriptseslint-config-react-appyarn.lockpre-commit. (@jdcrensh)react-scriptsCommitters: 26
Migrating from 1.0.10 to 1.0.11
Inside any created project that has not been ejected, run:
or
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: