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 Notesv1.0.15
1.0.15 (October 30, 2017)
🐛 Bug Fix
react-scripts
#3287 Fix favicon sizes value in the project manifest. (@ryansully)
react-dev-utils, react-scripts
#3230 Fix watching for changes in src/node_modules. (@xjlim)
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).
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)
react-scriptsreact-dev-utils,react-scriptssrc/node_modules. (@xjlim)react-scripts.mjsfiles. (@Timer)requestAnimationFramein test environment. (@gaearon)babel-preset-react-app,react-dev-utils,react-error-overlay,react-scriptsreact-dev-utils,react-error-overlaycreate-react-appUser Guide
npm-run-allto build Sass and JS. (@shime)README
Other
npm linkin tests. (@Timer)react-error-overlayreact-error-overlayin production. (@Timer)react-error-overlayhas no dependencies now (it's bundled). (@Timer)react-scriptsregisterServiceWorker.js. (@dunglas)output.pathfrom dev webpack config. (@nikolas)reason-reactsupport. (@lpalmes)style-loaderand disable inclusion of its HMR code in builds. (@insin)url-loaderto 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](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: