Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update dependency react-scripts to v2 - autoclosed #77

Closed
wants to merge 1 commit into from
Closed

Update dependency react-scripts to v2 - autoclosed #77

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 2, 2018 •
edited
Loading

This PR contains the following updates:

Package Type Update Change References
react-scripts dependencies major 1.1.4 -> 2.1.8 source

Release Notes

facebook/create-react-app

v2.1.8

Compare Source

v2.1.8 is a maintenance release that reapplies the TypeScript speed improvements (#​6406) in a new major version of react-dev-utils.

Migrating from 2.1.7 to 2.1.8

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

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

or

yarn add --exact react-scripts@2.1.8

v2.1.7

Compare Source

v2.1.7 is a maintenance release that temporarily reverts the TypeScript speed improvements (#​6406) to fix a dependency issue in react-dev-utils.

Migrating from 2.1.6 to 2.1.7

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

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

or

yarn add --exact react-scripts@2.1.7

v2.1.6

Compare Source

v2.1.6 is a maintenance release that brings a few new improvements, most notably:

  • 🚀 Reduced TypeScript rebuild times while running the development server. This was previously introduced in v2.1.4 but had to be reverted. Thanks to @​ianschmitz for getting this ready.
🐛 Bug Fix
💅 Enhancement
📝 Documentation
🏠 Internal
🔨 Underlying Tools
Committers: 15
Migrating from 2.1.5 to 2.1.6

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

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

or

yarn add --exact react-scripts@2.1.6

v2.1.5

Compare Source

v2.1.5 is a maintenance release that reverts the TypeScript speed improvements (#​5903) to fix a dependency issue in react-dev-utils.

Migrating from 2.1.4 to 2.1.5

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

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

or

yarn add --exact react-scripts@2.1.5

v2.1.4

Compare Source

v2.1.4 is a maintenance release that brings a number of awesome improvements. A few notable ones include:

  • 🚀 Reduced TypeScript rebuild times while running the development server. TypeScript is now blazing fast! Special thanks to @​deftomat and @​johnnyreilly and the other contributors for their hard work on this. (#​5903)
  • Jest type ahead support which provides a much nicer experience when filtering your tests using the Jest CLI (#​5213)
  • And many more improvements!
🐛 Bug Fix
💅 Enhancement
📝 Documentation
🏠 Internal
🔨 Underlying Tools
  • babel-preset-react-app, react-app-polyfill, react-dev-utils, react-scripts
  • babel-preset-react-app
  • eslint-config-react-app, react-scripts
Committers: 29
Migrating from 2.1.3 to 2.1.4

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

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

or

yarn add --exact react-scripts@2.1.4

v2.1.3

Compare Source

v2.1.3 is a maintenance release to fix a vulnerability in webpack-dev-server.

📝 Documentation
🏠 Internal
🔨 Underlying Tools
Committers: 8
Migrating from 2.1.2 to 2.1.3

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

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

or

yarn add --exact react-scripts@2.1.3

v2.1.2

Compare Source

v2.1.2 is a maintenance release including various bug fixes.

🚀 New Feature
  • babel-preset-react-app
🐛 Bug Fix
💅 Enhancement
📝 Documentation
🏠 Internal
Committers: 36
Migrating from 2.1.1 to 2.1.2

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

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

or

yarn add --exact react-scripts@2.1.2

v2.1.1

Compare Source

Happy Halloween 🎃 👻! This spooky release brings a treat: decorator support in TypeScript files!

🐛 Bug Fix
💅 Enhancement
📝 Documentation
🏠 Internal
Committers: 8
Migrating from 2.1.0 to 2.1.1

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

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

or

yarn add --exact react-scripts@2.1.1

v2.1.0

Compare Source

Create React App 2.1 adds support for TypeScript! Read the documentation to get started.

New applications can be created using TypeScript by running:

$ npx create-react-app my-app --typescript
🚀 New Feature
🐛 Bug Fix
💅 Enhancement
📝 Documentation
🏠 Internal
Committers: 15
Migrating from 2.0.5 to 2.1.0

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

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

or

yarn add --exact react-scripts@2.1.0

v2.0.5

Compare Source

🐛 Bug Fix
💅 Enhancement
📝 Documentation
🏠 Internal
Committers: 23
Migrating from 2.0.4 to 2.0.5

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

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

or

yarn add --exact react-scripts@2.0.5

v2.0.4

Compare Source

🐛 Bug Fix
💅 Enhancement
📝 Documentation
🏠 Internal
Committers: 11
Migrating from 2.0.3 to 2.0.4

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

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

or

yarn add --exact react-scripts@2.0.4

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.

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.

  • If you want to rebase/retry this PR, check this box

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

@coveralls
Copy link

coveralls commented Oct 2, 2018 •
edited
Loading

Coverage Status

Coverage remained the same at 100.0% when pulling ab4b68e on renovate/react-scripts-2.x into ee2b64e on master.

@renovate renovate bot force-pushed the renovate/react-scripts-2.x branch from 464f382 to f42d7be Compare October 3, 2018 20:06
@renovate renovate bot force-pushed the renovate/react-scripts-2.x branch from f42d7be to 2f89c45 Compare October 14, 2018 19:09
@renovate renovate bot force-pushed the renovate/react-scripts-2.x branch 2 times, most recently from fcbbd1c to b5bfbdb Compare November 1, 2018 03:41
@renovate renovate bot force-pushed the renovate/react-scripts-2.x branch from b5bfbdb to 73182aa Compare December 23, 2018 18:55
@renovate renovate bot force-pushed the renovate/react-scripts-2.x branch from 73182aa to e02aba7 Compare January 4, 2019 18:56
@renovate renovate bot force-pushed the renovate/react-scripts-2.x branch 2 times, most recently from 01ddf4d to 3dc0817 Compare February 11, 2019 18:44
@renovate renovate bot force-pushed the renovate/react-scripts-2.x branch 2 times, most recently from 3e512ee to 7ad6b5f Compare March 7, 2019 00:43
@renovate renovate bot force-pushed the renovate/react-scripts-2.x branch from 7ad6b5f to ab4b68e Compare March 7, 2019 00:56
@renovate renovate bot changed the title Update dependency react-scripts to v2 Update dependency react-scripts to v2 - autoclosed Apr 23, 2019
@renovate renovate bot closed this Apr 23, 2019
@renovate renovate bot deleted the renovate/react-scripts-2.x branch April 23, 2019 16:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@coveralls @renovate-bot