The version 0.5.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of react-dev-utils.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
You’ll also need to create a new folder called public in the root of your project. Then, move index.html and files it references (such as a favicon) into that folder.
You can no longer reference any files from ./src in index.html. Instead, public/index.html can now only reference files other inside of the public folder using a special variable called %PUBLIC_URL%.
This ensures it become a part of the build output, and resolves correctly both with client-side routing and non-root homepage in package.json. Read more about using the public folder and why these changes were made.
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 0.5.0 of react-dev-utils just got published.
The version 0.5.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of react-dev-utils. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
v0.5.00.5.0 (September 23, 2016)
Build Dependency (
react-scripts)publicfolder with arbitrary assets. (@gaearon in #703).envfile. (@ayrton in #695).babelrcand.eslintrc. (@fson in #689, @gaearon in #705)npm startdoesn’t fail in a composed Docker container. (@arekkas in #711)ejectare now cleaner. (@gaearon in #723)ESLint Config (
eslint-config-react-app)react/no-danger-with-childrenandreact/style-prop-objectrules. (@fson in #696)Babel Preset (
babel-preset-react-app)Utilities (
react-dev-utils)Global CLI (
create-react-app)READMEto npm. There were no other changes.Migrating from 0.4.3 to 0.5.0
Inside any created project that has not been ejected, run:
Breaking Changes in 0.5.0
Global ESLint Plugin Versions
If you used a global ESLint installation for the editor integration, you’ll need to install these versions of global ESLint packages.
Moving
index.htmlintopublicFolderYou’ll also need to create a new folder called
publicin the root of your project. Then, moveindex.htmland files it references (such as a favicon) into that folder.You can no longer reference any files from
./srcinindex.html. Instead,public/index.htmlcan now only reference files other inside of thepublicfolder using a special variable called%PUBLIC_URL%.For example, instead of:
You would need to move both
index.htmlandsrc/favicon.icointo thepublicfolder, and change<link>to look like this:This ensures it become a part of the build output, and resolves correctly both with client-side routing and non-root
homepageinpackage.json. Read more about using thepublicfolder and why these changes were made.Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: