0.2.1 (August 1, 2016)

Build Dependency (react-scripts)

• 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 linking react-scripts have been fixed (@dallonf in #277)
• We now use /static prefix for assets both in development and production (@gaearon in #278)

Migrating from 0.2.0 to 0.2.1

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.