-
Notifications
You must be signed in to change notification settings - Fork 0
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
Update react-scripts to the latest version 🚀 #15
base: master
Are you sure you want to change the base?
Conversation
Version 1.0.16 just got published.Update to this version instead 🚀 Release Notesv1.0.161.0.16 (October 31, 2017) 🎃🐛 Bug Fix
Committers: 2Migrating from 1.0.15 to 1.0.16Inside any created project that has not been ejected, run:
or
|
Version 1.0.17 just got published.Update to this version instead 🚀 Release Notesv1.0.171.0.17 (November 3, 2017)💅 Enhancement📝 Documentation
Committers: 3
Migrating from 1.0.16 to 1.0.17Inside any created project that has not been ejected, run:
or
|
Version 1.1.0 just got published.Update to this version instead 🚀 Release Notesv1.1.01.1.0 (January 15, 2018)🚀 New Feature
🐛 Bug Fix
💅 Enhancement
📝 Documentation
🏠 Internal
Committers: 47
Migrating from 1.0.17 to 1.1.0Inside any created project that has not been ejected, run:
or
|
Version 1.1.1 just got published. |
Version 1.1.2 just got published.Update to this version instead 🚀 Release Notesv1.1.21.1.2 (April 3, 2018)🐛 Bug Fix
📝 DocumentationCommitters: 2Migrating from 1.1.1 to 1.1.2Inside any created project that has not been ejected, run:
or
|
Version 1.1.3 just got published.Update to this version instead 🚀 Release Notesv1.1.31.1.3 (April 3, 2018)🐛 Bug Fix
Committers: 1
Migrating from 1.1.2 to 1.1.3Inside any created project that has not been ejected, run:
or
|
Version 1.1.4 just got published.Update to this version instead 🚀 Release Notesv1.1.41.1.4 (April 3, 2018)🐛 Bug FixCommitters: 1
Migrating from 1.1.3 to 1.1.4Inside any created project that has not been ejected, run:
or
|
Version 1.0.15 of react-scripts was just published.
The version 1.0.15 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.0.151.0.15 (October 30, 2017)
🐛 Bug Fix
react-scripts
react-dev-utils
,react-scripts
src/node_modules
. (@xjlim)💅 Enhancement
react-scripts
.mjs
files. (@Timer)requestAnimationFrame
in test environment. (@gaearon)babel-preset-react-app
,react-dev-utils
,react-error-overlay
,react-scripts
react-dev-utils
,react-error-overlay
create-react-app
📝 Documentation
User Guide
npm-run-all
to build Sass and JS. (@shime)README
🏠 Internal
Other
npm link
in tests. (@Timer)react-error-overlay
react-error-overlay
in production. (@Timer)react-error-overlay
has no dependencies now (it's bundled). (@Timer)react-scripts
registerServiceWorker.js
. (@dunglas)output.path
from dev webpack config. (@nikolas)reason-react
support. (@lpalmes)style-loader
and disable inclusion of its HMR code in builds. (@insin)url-loader
to 0.6.2 for mime ReDoS vulnerability. (@d3viant0ne)<!doctype html>
-><!DOCTYPE html>
. (@Hurtak)Committers: 24
Migrating from 1.0.14 to 1.0.15
Inside any created project that has not been ejected, run:
or
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 🌴