An in-range update of react-scripts is breaking the build 🚨

[greenkeeper]

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 1.1.3 of react-scripts was just published.

Branch	Build failing 🚨
Dependency	react-scripts
Current Version	1.1.2
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

react-scripts is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ✅ continuous-integration/travis-ci/push The Travis CI build passed Details
• ❌ ci/circleci Your tests failed on CircleCI Details

---

Release Notes

v1.1.3

1.1.3 (April 3, 2018)

🐛 Bug Fix

• react-scripts

  • #4247 Fix environment.dispose is not a function error caused by a Jest bug. (@gaearon)

Committers: 1

• Dan Abramov (gaearon)

Migrating from 1.1.2 to 1.1.3

Inside any created project that has not been ejected, run:

npm install --save --save-exact react-scripts@1.1.3

or

yarn add --exact react-scripts@1.1.3

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 🌴

[greenkeeper]

After pinning to 1.1.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[greenkeeper]

Version 1.1.4 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Release Notes

v1.1.4

1.1.4 (April 3, 2018)

🐛 Bug Fix

• react-dev-utils

  • #4250 Upgrade detect-port-alt to fix #4189. (@Timer)

Committers: 1

• Joe Haddad (Timer)

Migrating from 1.1.3 to 1.1.4

Inside any created project that has not been ejected, run:

npm install --save --save-exact react-scripts@1.1.4

or

yarn add --exact react-scripts@1.1.4