Open greenkeeper[bot] opened 5 years ago
After pinning to 2.1.3 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
devDependency
react-scripts was updated from 2.1.4
to 2.1.5
.Your tests are still failing with this version. Compare changes
devDependency
react-scripts was updated from 2.1.5
to 2.1.6
.Your tests are still failing with this version. Compare changes
v2.1.6 is a maintenance release that brings a few new improvements, most notably:
react-dev-utils
react-scripts
react-dev-utils
, react-scripts
create-react-app
yarn.lock.cached
if using the default Yarn registry. (@hangryCat)react-scripts
babel-preset-react-app
babel-preset-react-app
, confusing-browser-globals
, react-app-polyfill
create-react-app
react-dev-utils
source-map-explorer
docs to analyze all chunks. (@Kamahl19)react-dev-utils
, react-scripts
react-scripts
Inside any created project that has not been ejected, run:
npm install --save --save-exact react-scripts@2.1.6
or
yarn add --exact react-scripts@2.1.6
devDependency
react-scripts was updated from 2.1.6
to 2.1.7
.Your tests are still failing with this version. Compare changes
v2.1.7 is a maintenance release that temporarily reverts the TypeScript speed improvements (#6406) to fix a dependency issue in react-dev-utils
.
Inside any created project that has not been ejected, run:
npm install --save --save-exact react-scripts@2.1.7
or
yarn add --exact react-scripts@2.1.7
devDependency
react-scripts was updated from 2.1.7
to 2.1.8
.Your tests are still failing with this version. Compare changes
v2.1.8 is a maintenance release that reapplies the TypeScript speed improvements (#6406) in a new major version of react-dev-utils
.
Inside any created project that has not been ejected, run:
npm install --save --save-exact react-scripts@2.1.8
or
yarn add --exact react-scripts@2.1.8
The devDependency react-scripts was updated from
2.1.3
to2.1.4
.π¨ View failing branch.
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 failed ([Details](https://travis-ci.org/yhlben/react-kandian/builds/491379908?utm_source=github_status&utm_medium=notification)).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: