NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm · #4369 most downloaded on npm
ESLint configuration used by Create React App
Last release 2 years ago
no release in 18 months
Ships unpredictably
gaps range from 4 weeks to 2.8 years
Some releases are documented
notes for 21 of 41 stable releases
Nothing withdrawn
no release was ever pulled
10 years old
85 releases · first in 2016
react-dev-utils, react-error-overlay
react-scripts
NODE_PATH=src for npm start and npm run build. (@ApacheEx)NODE_PATH=src for Jest. (@gaearon)"homepage" field. (@gaearon).env.local in test environment. (@gaearon)react-dev-utils
react-dev-utils, react-error-overlay
react-error-overlay
eslint-config-react-app
react-scripts
<noscript> to template's index.html. (@viankakrisna)react-scripts
.env.* files are supported. (@AJamesPhillips)Inside any created project that has not been ejected, run:
npm install --save-dev --save-exact react-scripts@1.0.1
or
yarn add --dev --exact react-scripts@1.0.1
One column per quarter.
Please refer to the Jest 19 and Jest 20 breaking changes for migration instructions.
We’ve been working on this release for the past few months, and there are many big impovements, from migrating to webpack 2 to a brand new runtime error overlay and built-in support for Progressive Web Apps.
So instead of just enumerating them here, we decided to write a blog post about all the new features.
Check it out: What’s New in Create React App.
Have you read it? Now let's see how to update your app to the latest version.
First, ensure you are using the latest Node 6 LTS or newer. In 1.0.0, we have dropped support for Node 4 and NPM 2.
Inside any created project that has not been ejected, run:
npm install --save-dev --save-exact react-scripts@1.0.0
You may also optionally update the global command-line utility for bug fixes:
npm install -g create-react-app
src/We've never supported importing files from outside src/, nor have we supported running tests outside of src/.<br>
We also never explicitly forbid doing so, which caused confusion when things didn't work like they should.
When running or building your application, you may see a message like so:
You attempted to import ... which falls outside of the project src/ directory.
To remedy this, simply move any files that you import within src/ and update your relative imports accordingly. This enforces that files that import each other stay in src/, and other folders serve different purposes (e.g. the public/ folder just gets served from the root).
If you used relative imports outside the project directory as a way to share code with another project, consider using a monorepo instead, so that other projects are symlinked to your project's node_modules/. Then you can import them as a Node modules.
While running npm test, you may notice some of your tests are missing. Please move any top-level test directory (i.e. __test__, __spec__) or files (i.e. *.test.js, *.spec.js) into src/. Conversely, if you have some similarly named files that you don’t want Jest to run, move them outside of src/.
Moment.js locales are now purposely excluded from the bundle unless explicitly depended on.
Please import the locales you need:
import moment from 'moment';
import 'moment/locale/fr';
import 'moment/locale/es';
You can no longer import a file and expect to receive its contents as an encoded string.<br> This behavior was confusing and inconsistent depending on the file size.
Importing files with unknown extensions will now always include them into the build and return a valid URL.
If you'd like to import a file's contents as a string, consider contributing to #1944. For the time being, you must embed assets within an export:
// sample.txt
export default `i want
this data as a string
`;
You can then import this as so:
import sampleText from './sample.txt';
// ...
window qualifierPlease prefix any global method with window., you may experience this with methods such as confirm.
Simply update references from confirm to window.confirm.
Note that this new lint error will likely uncover legitimate accidental uses of global variables where you meant to define a local variable instead.
You can no longer use AMD import syntax, nor define an import anywhere other than the top of the file.
This is to reduce confusion around import statements, which do not allow you to evaluate code between them.
We have enabled a new set of rules to help make applications more accessible, please take time to learn about the errors and fix them.
You can search for every lint rule name in the right column and read its description on the web. The fixes are usually very simple.
We have enabled the lint warnings about React APIs deprecated in React 15.5. You can automatically convert your project to fix them by running the corresponding codemods.
Please refer to the Jest 19 and Jest 20 breaking changes for migration instructions.
If you use snapshots, you will likely need to update them once because of the change in format.
The old, 2009 specification for Flexbox is deprecated and is 2.3x slower than the latest specification.
We are no longer polyfilling it automatically.
Follow these steps if you see errors about missing lint rules in the editor.
npm install in your project (or yarn)If you still have the problem please file an issue.
After the regular update procedure above, add these line to <head> in public/index.html:
<meta name="theme-color" content="#000000">
<!--
manifest.json provides metadata used when your web app is added to the
homescreen on Android. See https://developers.google.com/web/fundamentals/engage-and-retain/web-app-manifest/
-->
<link rel="manifest" href="%PUBLIC_URL%/manifest.json">
Then create a file called public/manifest.json that looks like this:
{
"short_name": "React App",
"name": "Create React App Sample",
"icons": [
{
"src": "favicon.ico",
"sizes": "192x192",
"type": "image/png"
}
],
"start_url": "./index.html",
"display": "standalone",
"theme_color": "#000000",
"background_color": "#ffffff"
}
Finally, create src/registerServiceWorker.js with this template, import it from src/index.js and call the function it exports.
This was a large release, and we might have missed something.
Please file an issue and we will try to help.
Unhandled Promise rejections will now crash tests. You can fix them by explicitly catching the errors you don’t care about.
For a readable summary of the changes, check out our blog post.
react-dev-utils, react-scripts
react-scripts
src/ (#544). (@motevets)eslint-config-react-app, react-dev-utils
eslint-config-react-app, react-error-overlay, react-scripts
eslint-plugin-jsx-a11y and activate more rules. (@AlmeroSteyn)eslint-config-react-app, react-scripts
react-scripts
react-dev-utils, react-scripts
eslint-config-react-app, react-scripts
eslint-plugin-jsx-a11y and activate more rules. (@AlmeroSteyn)react-scripts
react-scripts and add require.resolve() to loaders. (@gaearon).eslintignore. (@Timer)localhost when offline (Windows). (@bunshar)http:// or https://. (@bunshar)detect-port. (@Andreyco)react-dev-utils
openBrowser now supports urls with more than one parameter. (@alisonmonteiro)openBrowser() when BROWSER=open on macOS. (@bpierre)cwd. (@chrisdrackett)create-react-app
react-dev-utils, react-scripts
react-dev-utils, react-error-overlay
react-scripts
yarn build instead of yarn run build. (@geoffdavis92)serve for running in production. (@leo)yarn instead of yarnpkg when creating a new application. (@lpalmes)X-FORWARDED headers for proxy requests. (@johann-sonntagbauer)eslint-config-react-app, react-dev-utils
react-error-overlay, react-scripts
babel-preset-react-app, eslint-config-react-app, react-dev-utils, react-error-overlay, react-scripts
eslint-config-react-app
eslint-config-react-app, react-scripts
react-dev-utils
create-react-app
react-scripts
.eslintrc effects. (@luftywiranda13).eslintrc for IDE lint plugins. (@gaearon)node-sass alternative. (@michaelwayman).env for enabling polling mode. (@gaearon)npm run watch-css command. (@mklemme)yarn.lock. (@viankakrisna)babel-preset-react-app
react-scripts
url import in Webpack config. (@pd4d10)react-dev-utils, react-scripts
babel-preset-react-app, react-scripts
create-react-app, react-dev-utils, react-scripts
appveyor.yml. (@Timer)babel-preset-react-app, create-react-app, eslint-config-react-app, react-dev-utils, react-scripts
eslint-config-react-app
eslint-config-react-app, react-dev-utils, react-scripts
react-dev-utils
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
Babel and ESLint configuration is now placed into package.json after ejecting. (@montogeek in #773)
react-scripts)package.json after ejecting. (@montogeek in #773)react-dev-utils)Inside any created project that has not been ejected, run:
npm install --save-dev --save-exact react-scripts@0.6.1
Adds an overlay for syntax errors in development. (@gaearon in #744)
react-scripts)react-dev-utils)Inside any created project that has not been ejected, run:
npm install --save-dev --save-exact react-scripts@0.6.0
Note: If the project fails to start, remove node_modules, ensure react-scripts is 0.6.0 in your package.json, and run npm install again. There seems to be an npm bug affecting this update.
This is the browser window when you make a syntax error:
Nothing published for this version
Updates react-dev-utils dependency
react-scripts)react-dev-utils dependencyreact-dev-utils)Inside any created project that has not been ejected, run:
npm install --save-dev --save-exact react-scripts@0.5.1
Adds support for `public` folder with arbitrary assets. (@gaearon in #703)
react-scripts)public folder with arbitrary assets. (@gaearon in #703).env file. (@ayrton in #695).babelrc and .eslintrc. (@fson in #689, @gaearon in #705)npm start doesn’t fail in a composed Docker container. (@arekkas in #711)eject are now cleaner. (@gaearon in #723)eslint-config-react-app)react/no-danger-with-children and react/style-prop-object rules. (@fson in #696)babel-preset-react-app)react-dev-utils)create-react-app)README to npm. There were no other changes.Inside any created project that has not been ejected, run:
npm install --save-dev --save-exact react-scripts@0.5.0
If you used a global ESLint installation for the editor integration, you’ll need to install these versions of global ESLint packages.
index.html into public FolderYou’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%.
For example, instead of:
<link rel="shortcut icon" href="./src/favicon.ico">
You would need to move both index.html and src/favicon.ico into the public folder, and change <link> to look like this:
<link rel="shortcut icon" href="%PUBLIC_URL%/favicon.ico">
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.
Breaking Change: Disabled implicit serving of source files in development. (@gaearon in #551)
react-scripts)NODE_PATH environment variable for absolute import paths. (@jimmyhmiller in #476)src/setupTests.js exists, it will be used to setup the test environment. (@gaelduplessix in #548)HTTPS environment variable is set to true, development server will run in HTTPS mode. (@dceddia in #552)Inside any created project that has not been ejected, run:
npm install --save-dev --save-exact react-scripts@0.4.0
Paths like /src/somefile.png used to be served in development, but only by accident. They never worked in production builds. Since 0.4.0, we don’t serve static files by default in development anymore either. This removes a dangerous inconsistency that we never intentionally supported.
If you need a static file to be part for the build, import it from JavaScript and you will get its filename. This ensures it gets included into the production build as well, and its filename contains the content hash.
If you used static files with <link href>, read this new guide on how to make sure these files get included into the builds. For example, you can replace <link href="/src/favicons/favicon-32.png"> with <link href="./src/favicons/favicon-32.png">, and then Webpack will recognize it and include it into the build.
If you referenced some other files from index.html, please file an issue to discuss your use case. In the meantime, you can serve them from a separate static server until your use case is supported.
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"
}
Nothing published for this version
Nothing published for this version
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
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →