do-react-app-a-create - npm Package Versions

2.0.4 (October 3, 2018)

:bug: 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)

:nail_care: Enhancement

• do-react-app-a-create
  • #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)

:memo: Documentation

• Other
  • #5228 removed do-react-app-a-create-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)

:house: 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)

2.0.3 (October 1, 2018)

Do React App A Create 2.0 brings a year’s worth of improvements in a single dependency update. We summarized all of the changes in a blog post!<br>

Check it out: Do React App A Create 2.0: Babel 7, Sass, and More.

It provides a high-level overview of new features and improvements. Now let's see how to update your app to the latest version in detail.

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 Do React App A Create 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);