The version 1.1.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 react-scripts.
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 Notesv1.1.0
1.1.0 (January 15, 2018)
🚀 New Feature
react-scripts
#3387 Add support for variable expansion in .env files. (@moos)
react-error-overlay
#3474 Allow the error overlay to be unregistered. (@Timer)
create-react-app
#3408 Add --info flag to help gather bug reports. (@tabrindle)
#3409 Add --use-npm flag to bypass Yarn even on systems that have it. (@tabrindle)
#3725 Extend --scripts-version to include .tar.gz format. (@SaschaDens)
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Coverage remained the same at 100.0% when pulling 77b6fc832571c8e71b4406fc1edefa27ed3badc0 on greenkeeper/react-scripts-1.1.0 into fcce4b84913331ea31894041a4f8ee15bdc19a90 on master.
Version 1.1.0 of react-scripts was just published.
The version 1.1.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 react-scripts.
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
v1.1.01.1.0 (January 15, 2018)
react-scripts
.env
files. (@moos)react-error-overlay
create-react-app
--info
flag to help gather bug reports. (@tabrindle)--use-npm
flag to bypass Yarn even on systems that have it. (@tabrindle)--scripts-version
to include.tar.gz
format. (@SaschaDens)"file:<path>"
--scripts-version
values. (@GreenGremlin)babel-preset-react-app
,react-scripts
react-dev-utils
GET
. (@doshisid)lsof
. (@rmccue)++
in the name. (@Norris1z)create-react-app
.npmrc
. (@mdogadailo)react-scripts
mjs
andjsx
filename extensions tofile-loader
exclude pattern. (@iansu)react-scripts
HOST
environment variable is set. (@iansu)create-react-app
react-dev-utils
code-insiders
to the editor list. (@shrynx)react-dev-utils
,react-error-overlay
react-dev-utils
,react-scripts
none
inREACT_EDITOR
environment variable. (@raerpo)eslint-config-react-app
no-cond-assign
rule. (@gaearon)User Guide
Other
eslint-config-react-app
href-no-hash
eslint rule. (@hazolsky)Other
cra.sh
development task to javascript. (@ianschmitz)dismissRuntimeErrors
function. (@skidding)printHostingInstructions
a bit. (@GreenGremlin)FileSizeReporter
for multi build Webpack setups. (@iiska)react-dev-utils
. (@xjlim)Committers: 47
Migrating from 1.0.17 to 1.1.0
Inside any created project that has not been ejected, run:
or
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: