NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm · #4861 most downloaded on npm
Babel plugin for named asset imports in Create React App
Last release 4 years ago
no release in 18 months
Release timing varies
gaps range from 3 weeks to 10 months
Some releases are documented
notes for 6 of 14 stable releases
Nothing withdrawn
no release was ever pulled
9 years old
43 releases · first in 2018
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Bumps Jest dependency to fix a few issues discovered yesterday. (@cpojer in facebook/jest#1580, @insin in facebook/jest#1574)
react-scripts)Inside any created project that has not been ejected, run:
npm install --save-dev --save-exact react-scripts@0.3.1
Nothing published for this version
Breaking Change: Local paths in in index.html will now be correctly resolved, so deleting favicon.ico is not an error anymore. (@andreypopp in #428)
react-scripts)src directory. (@fson in #504)<link href> in index.html will now be correctly resolved, so deleting favicon.ico is not an error anymore. (@andreypopp in #428)<div ref={node => this.node = node}>. (@mrscobbler in #529)react-constant-elements Babel transform because of its bugs. (@gaearon in #534)create-react-app).idea folder, which is necessary for future WebStorm integration. (@denofevil in #522)You may optionally update the global command (it’s not required):
npm install -g create-react-app@0.3.0
Inside any created project that has not been ejected, run:
npm install --save-dev --save-exact react-scripts@0.3.0
Now favicon.ico is not treated specially anymore.
If you use it, move it to src and add the following line to <head> in your HTML:
<link rel="shortcut icon" href="./src/favicon.ico">
Since 0.3.0 added a test runner, we recommend that you add it to the scripts section of your package.json like this:
// ...
"scripts": {
// ...
"test": "react-scripts test --env=jsdom"
}
You can now proxy requests to an API server without worrying about CORS. (@gaearon in #282)
react-scripts)async and await syntax. (@gaearon in #327, @fson in #332).webp extension are now supported. (@gafemoyano in #458)package.json. (@wdhorton in #477)Update react-scripts to point to 0.2.3 in your package.json and run npm install. You shouldn’t need to do anything else.
Newly created projects will use 0.2.3 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.
Nothing published for this version
Nothing published for this version
When the bundle size changes, we now display the difference after build. (@elijahmanor in #340)
react-scripts)npm installing a missing dependency now forces a rebuild. (@gaearon in #349)Object.assign() polyfill is now bundled by default. (@gaearon in #399)otf font format is now supported. (@A-gambit in #434)new-cap linting rule has been disabled thanks to feedback from Immutable.js users. (@rricard in #470)Update react-scripts to point to 0.2.2 in your package.json and run npm install. You shouldn’t need to do anything else.
Newly created projects will use 0.2.2 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.
Fixes an issue with npm start taking a very long time on OS X with Firewall enabled (@gaearon in #319)
react-scripts)npm start taking a very long time on OS X with Firewall enabled (@gaearon in #319)?v= after asset filenames, such as Font Awesome, now works correctly (@alexzherdev in #298)npm linking react-scripts have been fixed (@dallonf in #277)/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 to package.json (@dhruska in #94)
react-scripts)homepage field to package.json (@dhruska in #94)0.0.0.0 and works with VirtualBox (@JWo1F in #128)3000 port is taken, we offer to use another port (@chocnut in #101, 2edf21)import CSS files from npm modules (@glennreyes in #105, @breaddevil in #178)fetch and Promise polyfills are now always included (@gaearon in #235).gitignore (@npverni in #79, @chibicode in #112).babelrc in parent directory no longer causes an error (@alexzherdev in #236).json extension are now discovered (@gaearon in a11d6a)create-react-app)--version flag correctly (@mxstbr in #152)You may optionally update the global command (it’s not required):
npm install -g create-react-app@0.2.0
Inside any created project that has not been ejected, run:
npm install --save-dev --save-exact react-scripts@0.2.0
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.
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →