Changelog for 0.2.0

[gaearon]

0.2.0

Build Dependency (react-scripts)

• You can now enable deployment to GitHub Pages by adding homepage field to package.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 and Promise 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)

Global CLI (create-react-app)

• It enforces that you have Node >= 4 (@conorhastings in #88)
• It handles --version flag correctly (@mxstbr in #152)

Migrating from 0.1.0 to 0.2.0

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.

[vjeux]

Generated ESLint configuration is now compatible with IDEs with npm 3 (@keyanzhang in #149)

This shouldn't be in the global cli section. This change will be picked up with the new release even if you don't update the global cli

[gaearon]

Ah you're right, can you fix this please? I keep forgetting about the split :P

[vjeux]

Hopefully from now on we're never going to change the global cli, ever ;)