NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm · #4696 most downloaded on npm
Polyfills for various browsers including commonly used language features
Last release 2 years ago
no release in 18 months
Ships unpredictably
gaps range from 3 weeks to 2.8 years
Most releases are documented
notes for 11 of 17 stable releases
Nothing withdrawn
no release was ever pulled
8 years old
41 releases · first in 2018
Nothing published for this version
Nothing published for this version
Like any major release, react-scripts@3.0.0 contains a few breaking changes. We expect that they won't affect every user, but we recommend you look ov…
Create React App 3.0 brings some exciting new features including support for Hooks!
Thanks to all the maintainers and contributors who worked so hard on this release! :tada:
browserslist support in @babel/preset-env: #6608jsconfig.json/tsconfig.json: #6656Inside any created project that has not been ejected, run:
npm install --save --save-exact react-scripts@3.0.0
or
yarn add --exact react-scripts@3.0.0
If you previously ejected but now want to upgrade, one common solution is to find the commits where you ejected (and any subsequent commits changing the configuration), revert them, upgrade, and later optionally eject again. It’s also possible that the feature you ejected for is now supported out of the box.
Like any major release, react-scripts@3.0.0 contains a few breaking changes. We expect that they won't affect every user, but we recommend you look over this section to see if something is relevant to you. If we missed something, please file a new issue.
We've updated from Jest 23 to get the latest improvements in Jest 24. We've noticed some differences in snapshot serialization in Jest 24, so you may need to adjust your tests slightly once you update. You can read more about what's changed in the Jest 24 blog post.
We now enforce Rules of Hooks with eslint-plugin-react-hooks. If you are breaking any of the rules of Hooks this will cause your build to fail.
We now lint TypeScript files. You can see the list of rules we enforce to check if your project is compatible. If you're using Visual Studio Code you can follow our guide to setup up your editor to display lint warnings.
browserslist support in @babel/preset-envThe browserslist config in your package.json is now used to control the output of your JavaScript files. You can use separate configuration for development and production. See here for a good starting point which gives a good development experience, especially when using language features such as async/await, but still provides high compatibility with many browsers in production
We've removed the --no-watch flag from the start script in favor of Jest's own --watchAll=false.
asset-manifest.jsonAll asset paths have been moved under the files key in asset-manifest.json.
jsconfig.json/tsconfig.jsonWe now support setting baseUrl in jsconfig.json and tsconfig.json. To configure baseUrl to point to the src directory in your JavaScript project, create a jsconfig.json file in your project root:
```json
{
"compilerOptions": {
"baseUrl": "src"
},
"include": ["src"]
}
```
If you have a TypeScript project you can configure baseUrl the same way in your tsconfig.json.
Currently the only supported options for baseUrl are node_modules (the default) and src.
You can now include a version of Normalize.css in your project that will use your browserslist setting to generate the appropriate styles for your target browsers. To include it simply add @import-normalize at the top of one of your CSS files.
react-scripts
babel-plugin-named-asset-import, confusing-browser-globals, react-dev-utils, react-error-overlay, react-scripts
eslint-config-react-app, react-scripts
babel-preset-react-app, eslint-config-react-app, react-scripts
babel-preset-react-app, react-dev-utils, react-scripts
react-scripts
babel-preset-react-app, react-app-polyfill
babel-plugin-named-asset-import, confusing-browser-globals, react-dev-utils, react-error-overlay, react-scripts
eslint-config-react-app, react-scripts
babel-preset-react-app, eslint-config-react-app, react-scripts
babel-preset-react-app, react-dev-utils, react-scripts
react-dev-utils
react-scripts
create-react-app
react-scripts
react-scripts eject warning. (@lffg)babel-plugin-named-asset-import, babel-preset-react-app, confusing-browser-globals, create-react-app, eslint-config-react-app, react-app-polyfill, react-dev-utils, react-error-overlay, react-scripts
babel-preset-react-app, react-app-polyfill
create-react-app
react-dev-utils
react-scripts
react-scripts
babel-plugin-named-asset-import, confusing-browser-globals, react-dev-utils, react-error-overlay, react-scripts
react-dev-utils
eslint-config-react-app
react-scripts
babel-plugin-named-asset-import, babel-preset-react-app, confusing-browser-globals, create-react-app, eslint-config-react-app, react-app-polyfill, react-dev-utils, react-error-overlay, react-scripts
babel-preset-react-app
babel-preset-react-app, react-dev-utils, react-error-overlay, react-scripts
react-dev-utils
eslint-config-react-app
eslint-config-react-app, react-scripts
babel-preset-react-app, eslint-config-react-app, react-scripts
babel-preset-react-app, create-react-app, react-app-polyfill, react-dev-utils, react-error-overlay, react-scripts
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
eslint-config-react-app, react-error-overlay, react-scripts
eslint-config-react-app, react-error-overlay, react-scripts
react-dev-utils
react-scripts
/__* URLs to fix Firebase hosting. (@ryansully)README
Inside any created project that has not been ejected, run:
npm install --save-dev --save-exact react-scripts@1.0.6
or
yarn add --dev --exact react-scripts@1.0.6
Inside any created project that has not been ejected, run:
react-dev-utils, react-scripts
react-dev-utils
eslint-config-react-app
Inside any created project that has not been ejected, run:
npm install --save-dev --save-exact react-scripts@1.0.5
or
yarn add --dev --exact react-scripts@1.0.5
Fix a regression in published package.
react-error-overlay
Inside any created project that has not been ejected, run:
npm install --save-dev --save-exact react-scripts@1.0.4
or
yarn add --dev --exact react-scripts@1.0.4
react-dev-utils, react-error-overlay
react-dev-utils
eslint-config-react-app
react-dev-utils, react-error-overlay
console calls into a check. (@BrodaNoel)react-scripts
Inside any created project that has not been ejected, run:
npm install --save-dev --save-exact react-scripts@1.0.3
or
yarn add --dev --exact react-scripts@1.0.3
react-dev-utils, react-error-overlay
react-dev-utils, react-scripts
react-dev-utils, react-error-overlay
react-dev-utils
react-scripts
git status. (@milocosmopolitan)Inside any created project that has not been ejected, run:
npm install --save-dev --save-exact react-scripts@1.0.2
or
yarn add --dev --exact react-scripts@1.0.2
If you previously had issues with an Invalid Host Header error, follow these new instructions to fix it.
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
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
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.
Nothing published for this version
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
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
Your coding agent can read these notes before it upgrades. Set up the MCP server →