chore(deps): update dependency react-scripts to v2

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	References
react-scripts	devDependencies	major	1.1.5 -> 2.0.4	source

---

Release Notes

facebook/create-react-app

v2.0.4

Compare Source

🐛 Bug Fix

• react-scripts
  • #​5281 Fix code minifying (@​Timer)
  • #​5246 Fix GENERATE_SOURCEMAP env not working for css sourcemap (@​crux153)
• babel-preset-react-app
  • #​5278 Disable Symbol typeof transform (@​gaearon)

💅 Enhancement

• create-react-app
  • #​5270 Caches the Yarn resolution for faster installs (@​arcanis)
  • #​5269 Adds a version check when using --use-pnp (@​arcanis)
• react-scripts
  • #​5258 Add .mjs support back to webpack (@​Timer)

📝 Documentation

• Other
  • #​5228 removed create-react-app-parcel link (@​lockround)
  • #​5254 Update README links for CSS modules and SASS (@​yuyokk)
  • #​5249 Set the color palette to something a bit more React-y (@​selbekk)
  • #​5244 Update favicon and OpenGraph images (@​selbekk)
  • #​5242 5238 Removing sample pages (@​selbekk)
  • #​5243 Set the project name and owner correctly (@​selbekk)
  • #​5239 5238 removing blog from Docusaurus (@​selbekk)
  • #​5227 Initial setup of Docusaurus (@​amyrlam)
• react-scripts
  • #​5252 Revert change to http-proxy-middleware docs (@​iansu)
  • #​5226 Fix usage of http-proxy-middleware (@​banyan)
  • #​5233 DOCS: Add Relay example (@​zachasme)

🏠 Internal

• #​5263 Add browser test for graphql (@​Timer)

Committers: 11

• Amy Lam (@​amyrlam)
• Crux (@​crux153)
• Dan Abramov (@​gaearon)
• Ian Sutherland (@​iansu)
• Iurii Kucherov (@​yuyokk)
• Joe Haddad (@​Timer)
• Kohei Hasegawa (@​banyan)
• Kristofer Selbekk (@​selbekk)
• Maël Nison (@​arcanis)
• Shubham Tiwari (@​lockround)
• Zacharias Knudsen (@​zachasme)

v2.0.3

Compare Source

Inside any created project that has not been ejected, run:

npm install --save --save-exact react-scripts@2.0.3

or

yarn add --exact react-scripts@2.0.3 

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 (maybe Sass or CSS Modules?) is now supported out of the box. You can find a list of notable new features in the Create React App 2.0 blog post.

Breaking Changes

Like any major release, react-scripts@2.0 contains a few breaking changes. We expect that they won't affect every user, but we recommend to scan over these sections to see if something is relevant to you. If we missed something, please file a new issue.

Node 6 is no longer supported

Please upgrade to Node 8 (LTS) or later.

Polyfills for IE 9, IE 10, and IE 11 are no longer included by default (but you can opt in!)

We have dropped default support for Internet Explorer 9, 10, and 11. If you still need to support these browsers, follow the instructions below.

First, install react-app-polyfill:

npm install react-app-polyfill

or

yarn add react-app-polyfill 

Next, place one of the following lines at the very top of src/index.js:

import 'react-app-polyfill/ie9'; // For IE 9-11 support import 'react-app-polyfill/ie11'; // For IE 11 support

You can read more about these polyfills here.

Dynamic import() of a CommonJS module now has a .default property

Webpack 4 changed the behavior of import() to be closer in line with the specification.

Previously, importing a CommonJS module did not require you specify the default export. In most cases, this is now required.
If you see errors in your application about ... is not a function, you likely need to update your dynamic import, e.g.:

const throttle = await import('lodash/throttle'); // replace with const throttle = await import('lodash/throttle').then(m => m.default);

require.ensure() is superseded by dynamic import()

We previously allowed code splitting with a webpack-specific directive, require.ensure(). It is now disabled in favor of import(). To switch to import(), follow the examples below:

Single Module

require.ensure(['module-a'], function() { var a = require('module-a'); // ... }); // Replace with: import('module-a').then(a => { // ... });

Multiple Module

require.ensure(['module-a', 'module-b'], function() { var a = require('module-a'); var b = require('module-b'); // ... }); // Replace with: Promise.all([import('module-a'), import('module-b')]).then(([a, b]) => { // ... });

The default Jest environment was changed to jsdom

Look at the test entry in the scripts section of your package.json.
Here's a table how to change it from "before" and "after", depending on what you have there:

1.x (if you have this...)	2.x (...change it to this!)
react-scripts test --env=jsdom	react-scripts test
react-scripts test	react-scripts test --env=node

Object proxy configuration is superseded by src/setupProxy.js

To check if action is required, look for the proxy key in package.json and follow this table:

1. I couldn't find a proxy key in package.json
   • No action is required!
2. The value of proxy is a string (e.g. http://localhost:5000)
   • No action is required!
3. The value of proxy is an object
   • Follow the migration instructions below.

It's worth highlighting: if your proxy field is a string, e.g. http://localhost:5000, or you don't have it, skip this section. This feature is still supported and has the same behavior.

If your proxy is an object, that means you are using the advanced proxy configuration. It has become fully customizable so we removed the limited support for the object-style configuration. Here's how to recreate it.

First, install http-proxy-middleware using npm or Yarn:

npm install http-proxy-middleware

or

yarn add http-proxy-middleware 

Next, create src/setupProxy.js and place the following contents in it:

const proxy = require('http-proxy-middleware'); module.exports = function(app) { // ... };

Now, migrate each entry in your proxy object one by one, e.g.:

"proxy": { "/api": { "target": "http://localhost:5000/" }, "/*.svg": { "target": "http://localhost:5000/" } }

Place entries into src/setupProxy.js like so:

const proxy = require('http-proxy-middleware'); module.exports = function(app) { app.use(proxy('/api', { target: 'http://localhost:5000/' })); app.use(proxy('/*.svg', { target: 'http://localhost:5000/' })); };

You can also use completely custom logic there now! This wasn't possible before.

.mjs file extension support is removed

Change the extension of any files in your project using .mjs to just .js.

It was removed because of inconsistent support from underlying tools. We will add it back after it stops being experimental, and Jest gets built-in support for it.

PropTypes definitions are now removed in production

Normally, this shouldn't affect your logic and should make the resulting bundle smaller. However, you may be relying on PropTypes definition for production logic. This is not recommended, and will break now. If a library does it, one possible solution is to file an issue in it with a proposal to use a different field (not propTypes) to signal that the declaration needs to be retained.

Anything missing?

This was a large release, and we might have missed something.

Please file an issue and we will try to help.

---

Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

This PR has been generated by Renovate Bot. View repository job log here.

[vercel]

This pull request is automatically deployed with Now.
To access deployments, click Details below or on the icon next to each push.