-
-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An in-range update of react-scripts is breaking the build 🚨 #9
Comments
After pinning to 3.0.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.1.03.1.0 (2019-08-09)v3.1.0 is a minor release that adds ESLint 6 support as well as experimental support for extended and customizing the ESLint config along with other minor bug fixes and documentation updates. Highlights
🚀 New Feature
💥 Breaking Change
🐛 Bug Fix
💅 Enhancement
📝 Documentation
🏠 Internal
🔨 Underlying Tools
Committers: 46
Migrating from 3.0.1 to 3.1.0Inside any created project that has not been ejected, run: npm install --save --save-exact [email protected] or yarn add --exact [email protected] |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.1.13.1.1 (2019-08-13)v3.1.1 is a maintenance release that includes minor bug fixes and documentation updates. 🐛 Bug Fix
💅 Enhancement📝 DocumentationCommitters: 3
Migrating from 3.1.0 to 3.1.1Inside any created project that has not been ejected, run: npm install --save --save-exact [email protected] or yarn add --exact [email protected] |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.2.03.2.0 (2019-10-03)v3.2.0 is a minor release that adds support for production profiling and ignoring TypeScript type errors to make migrating JavaScript projects to TypeScript easier. It also includes other minor bug fixes and documentation updates. 🚀 New Feature
🐛 Bug Fix
💅 Enhancement
📝 Documentation
🏠 Internal
🔨 Underlying Tools
Committers: 19
Migrating from 3.1.2 to 3.2.0Inside any created project that has not been ejected, run: npm install --save --save-exact [email protected] or yarn add --exact [email protected] |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.3.03.3.0 (2019-12-04)v3.3.0 is a minor release that adds new features, including custom templates and support for the new optional chaining and nullish coalescing operators. Custom TemplatesYou can now create a new app using custom templates. We've published our existing templates as The below command shows how you can create a new app with npx create-react-app my-app --template typescript Note that you can omit the prefix If you don't set a template, we'll create your new app with Optional Chaining and Nullish Coalescing OperatorsWe now support the optional chaining and nullish coalescing operators! // Optional chaining a?.(); // undefined if `a` is null/undefined b?.c; // undefined if `b` is null/undefined If your're using TypeScript, you will need to upgrade your If you're using Visual Studio Code 1.40 (the latest as of this release) or earlier, you will need to configure your editor if you want it to understand the new operators. If you're using TypeScript in your project and have already upgrade its version as described above, then you can configure VS Code to Numeric SeparatorsWe've added support for numeric separators to improve readability of numeric literals. 1000000000; // Is this a billion? a hundred millions? Ten millions? 101475938.38; // what scale is this? what power of 10? no-unexpected-multilineWe've removed this rule as it is not compatible with Prettier. If you rely on this rule you can re-enable it by extending our ESLint config and adding the following: { "extends": "react-app", "rules": { "no-unexpected-multiline": "warn" } } 🚀 New Feature
💥 Breaking Change
🐛 Bug Fix
💅 Enhancement
📝 Documentation
🏠 Internal
🔨 Underlying Tools
Committers: 42
Migrating from 3.2.0 to 3.3.0Inside any created project that has not been ejected, run: npm install --save --save-exact [email protected] or yarn add --exact [email protected] |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.3.13.3.1 (2020-01-31)v3.3.1 is a maintenance release that includes minor bug fixes and documentation updates. 🐛 Bug Fix
💅 Enhancement
📝 Documentation
🏠 Internal
🔨 Underlying Tools
Committers: 29
Migrating from 3.3.0 to 3.3.1Inside any created project that has not been ejected, run: npm install --save --save-exact [email protected] or yarn add --exact [email protected] |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.4.03.4.0 (2020-02-14)v3.4.0 is a minor release that adds new features, including support for SSL and setting 🐛 Bug Fix
💅 Enhancement
📝 Documentation
🔨 Underlying Tools
Committers: 18
Migrating from 3.3.1 to 3.4.0Inside any created project that has not been ejected, run: npm install --save --save-exact [email protected] or yarn add --exact [email protected] |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v3.4.13.4.1 (2020-03-20)v3.4.1 is a maintenance release that includes minor bug fixes and documentation updates including upgrading Babel to fix a bug in the 7.8 release line. This release also brings support for TypeScript 3.8. 🐛 Bug Fix
💅 Enhancement
📝 Documentation
🔨 Underlying Tools
Committers: 9
Migrating from 3.4.0 to 3.4.1Inside any created project that has not been ejected, run: npm install --save --save-exact [email protected] or yarn add --exact [email protected] |
The dependency react-scripts was updated from
3.0.0
to3.0.1
.🚨 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 direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
Status Details
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 🌴
The text was updated successfully, but these errors were encountered: