The version 1.1.2 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.1.2
1.1.2 (April 3, 2018)
š Bug Fix
react-scripts
#4085 Resolve .js before .mjs files to unbreak dependencies with native ESM support. (@leebyron)
š Documentation
react-scripts
#4197 Add troubleshooting for Github Pages. (@xnt)
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).
Coverage remained the same at 100.0% when pulling 37fed27d3f058e776e28a56685d5b752f8293f7b on greenkeeper/react-scripts-1.1.2 into e29e07d5c28770d26574071488af1314cd3e860b on master.
āļø Greenkeeperās updated Terms of Service will come into effect on April 6th, 2018.
Version 1.1.2 of react-scripts was just published.
The version 1.1.2 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.1.21.1.2 (April 3, 2018)
react-scripts
.js
before.mjs
files to unbreak dependencies with native ESM support. (@leebyron)react-scripts
Committers: 2
Migrating from 1.1.1 to 1.1.2
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: