- Fixes an issue with
npm start
taking a very long time on OS X with Firewall enabled (@gaearon in #319) - Fixes an issue with Webpack eating a lot of CPU in some cases (@dceddia in #294)
- We now warn if you import a file with mismatched casing because this breaks the watcher (@alexzherdev in #266)
- CSS files specifying
?v=
after asset filenames, such as Font Awesome, now works correctly (@alexzherdev in #298) - Issues with
npm link
ingreact-scripts
have been fixed (@dallonf in #277) - We now use
/static
prefix for assets both in development and production (@gaearon in #278)
Update react-scripts
to point to 0.2.1
in your package.json
and run npm install
. You shouldn’t need to do anything else. If you see a warning about wrong file casing next time you npm start
, fix your imports to use the correct filename casing.
Newly created projects will use 0.2.1
automatically. You don’t need to update the global create-react-app
CLI itself. It stays at 0.2.0
for now because it doesn’t have any changes.
- You can now enable deployment to GitHub Pages by adding
homepage
field topackage.json
(@dhruska in #94) - Development server now runs on
0.0.0.0
and works with VirtualBox (@JWo1F in #128) - Cloud9 and Nitrous online IDEs are now supported (@gaearon in 2fe84e)
- When
3000
port is taken, we offer to use another port (@chocnut in #101, 2edf21) - You can now
import
CSS files from npm modules (@glennreyes in #105, @breaddevil in #178) fetch
andPromise
polyfills are now always included (@gaearon in #235)- Regenerator runtime is now included if you use ES6 generators (@gaearon in #238)
- Generated project now contains
.gitignore
(@npverni in #79, @chibicode in #112) - ESLint config is now more compatible with Flow (@gaearon in #261)
- A stylistic lint rule about method naming has been removed (@mxstbr in #152)
- A few unobtrusive accessibility lint rules have been added (@evcohen in #175)
- A
.babelrc
in parent directory no longer causes an error (@alexzherdev in #236) - Files with
.json
extension are now discovered (@gaearon in a11d6a) - Bug fixes from transitive dependencies are included (#126)
- Linting now works with IDEs if you follow these instructions (@keyanzhang in #149)
- After building, we now print gzipped bundle size (@lvwrence in #229)
- It enforces that you have Node >= 4 (@conorhastings in #88)
- It handles
--version
flag correctly (@mxstbr in #152)
You may optionally update the global command (it’s not required):
npm install -g [email protected]
Inside any created project that has not been ejected, run:
npm install --save-dev --save-exact [email protected]
You may need to fix a few lint warnings about missing <img alt>
tag, but everything else should work out of the box. If you intend to deploy your site to GitHub Pages, you may now add homepage
field to package.json
. If you had issues with integrating editor linter plugins, follow these new instructions.
- Initial public release