Skip to content

Latest commit

 

History

History
384 lines (247 loc) · 27.7 KB

CHANGELOG.md

File metadata and controls

384 lines (247 loc) · 27.7 KB
Raw

0.6.1 (September 27, 2016)

Build Dependency (react-scripts)

  • Babel and ESLint configuration is now placed into package.json after ejecting. (@montogeek in #773)

Utilities (react-dev-utils)

  • Fixes the syntax error overlay padding. (@fson in #758)

Migrating from 0.6.0 to 0.6.1

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

npm install --save-dev --save-exact react-scripts@0.6.1

0.6.0 (September 25, 2016)

Build Dependency (react-scripts)

  • Adds an overlay for syntax errors in development. (@gaearon in #744)

Utilities (react-dev-utils)

  • Adds an alternative WebpackDevServer client that displays the error overlay. (@gaearon in #744)

Migrating from 0.5.1 to 0.6.0

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.

0.5.1 (September 23, 2016)

Build Dependency (react-scripts)

  • Updates react-dev-utils dependency

Utilities (react-dev-utils)

  • Fixes %PUBLIC_URL% replacement to work when specified multiple times. (@fson in #731)

Migrating from 0.5.0 to 0.5.1

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

npm install --save-dev --save-exact react-scripts@0.5.1

0.5.0 (September 23, 2016)

Build Dependency (react-scripts)

ESLint Config (eslint-config-react-app)

Babel Preset (babel-preset-react-app)

  • Published for the first time! (@fson in #701)

Utilities (react-dev-utils)

Global CLI (create-react-app)

  • Added README to npm. There were no other changes.

Migrating from 0.4.3 to 0.5.0

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

npm install --save-dev --save-exact react-scripts@0.5.0

Breaking Changes in 0.5.0

Global ESLint Plugin Versions

If you used a global ESLint installation for the editor integration, you’ll need to install these versions of global ESLint packages.

Moving index.html into public Folder

You’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.

0.4.3 (September 18, 2016)

This is a hotfix release for a broken package.
It contained no changes to the code.

Build Dependency (react-scripts)

  • Fixes a packaging issue that affected npm 2. (#676)

Migrating from 0.4.2 to 0.4.3

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

npm install --save-dev --save-exact react-scripts@0.4.3

0.4.2 (September 18, 2016)

Build Dependency (react-scripts)

  • Lint output in editor is now opt-in because, due to this ESLint issue, it is broken by default in Atom. (@fson in #649)
  • Fixes an issue causing compile errors when project folder is inside a symlink. (@motiz88 in #648)
  • You can now import jpeg, wav, mp3, m4a, aac, and oga. (@mareksuscak in #624, @danharper in #665)
  • Fixes false positives caused by the case sensitive import warning on Windows. (@Urthen in #593)
  • With Docker, *.json.gzip files are no longer created in the project folder. (@thangngoc89 in #620)
  • Proxy network errors now abort requests instead of hanging. (@cloudmu in #588)
  • Connection to the development server does not get interrupted in HTTPS mode. (@dceddia in #652)
  • Unsupported Node versions now print a warning. (@fson in #575)
  • Importing assets with special characters like @ now works with tests. (@fson in #584)
  • Undefined variable lint rule is promoted from a warning to an error. (@gaearon in #669)
  • Variables starting with underscore no longer trigger the “unused variable” rule. (@valscion in #640)
  • We now print a friendly error when required files are missing. (@vnctaing in #653)
  • The output after creating a project is better formatted. (@btnwtn in #629)
  • Development server logs are less noisy. (@gaearon in 122068)

Global CLI (create-react-app)

  • It now runs on early Node versions to print a friendly warning instead of crashing. (@sotojuan in fc3ab4)
  • We now print a friendly message when you create a project with invalid name. (@mareksuscak in #628)
  • Passing a custom fork of react-scripts to create-react-app with --scripts-version works again. (@yesmeck in #632)

Migrating from 0.4.1 to 0.4.2

You may optionally update the global command (it’s not required):

npm install -g create-react-app@0.4.2

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

npm install --save-dev --save-exact react-scripts@0.4.2

0.4.1 (September 3, 2016)

Build Dependency (react-scripts)

Migrating from 0.4.0 to 0.4.1

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

npm install --save-dev --save-exact react-scripts@0.4.1

0.4.0 (September 2, 2016)

Build Dependency (react-scripts)

  • Breaking Change: Disabled implicit serving of source files in development. (@gaearon in #551)
  • You can use NODE_PATH environment variable for absolute import paths. (@jimmyhmiller in #476)
  • If src/setupTests.js exists, it will be used to setup the test environment. (@gaelduplessix in #548)
  • If HTTPS environment variable is set to true, development server will run in HTTPS mode. (@dceddia in #552)

Migrating from 0.3.1 to 0.4.0

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

npm install --save-dev --save-exact react-scripts@0.4.0

Breaking Change in 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.

0.3.1 (September 2, 2016)

Build Dependency (react-scripts)

Migrating from 0.3.0 to 0.3.1

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

npm install --save-dev --save-exact react-scripts@0.3.1

0.3.0 (September 1, 2016)

Build Dependency (react-scripts)

Global CLI (create-react-app)

  • You can now create a project in a folder that already contains an .idea folder, which is necessary for future WebStorm integration. (@denofevil in #522)

Migrating from 0.2.3 to 0.3.0

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

Breaking Change

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">

New Feature

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"
  }

Then read the testing guide to learn more about using it!

0.2.3 (August 25, 2016)

Build Dependency (react-scripts)

Migrating from 0.2.2 to 0.2.3

Update react-scripts to point to 0.2.3 in your package.json and run npm install. You shouldn’t need to do anything else.

Newly created projects will use 0.2.3 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.

0.2.2 (August 22, 2016)

Build Dependency (react-scripts)

  • When the bundle size changes, we now display the difference after build. (@elijahmanor in #340)
  • npm installing a missing dependency now forces a rebuild. (@gaearon in #349)
  • Autoprefixer config now includes more commonly supported browsers. (@kripod in #345)
  • All the configuration is now documented inline so ejecting doesn’t leave you in the dark. (@gaearon in #362)
  • Object.assign() polyfill is now bundled by default. (@gaearon in #399)
  • React Native Web now works out of the box. (@grigio in #407)
  • Same asset filenames in different folders don’t confuse the server now. (@arunoda in #446)
  • The otf font format is now supported. (@A-gambit in #434)
  • The new-cap linting rule has been disabled thanks to feedback from Immutable.js users. (@rricard in #470)

Migrating from 0.2.1 to 0.2.2

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.

0.2.1 (August 1, 2016)

Build Dependency (react-scripts)

  • Fixes an issue with npm start taking a very long time on OS X with Firewall enabled (@gaearon in #319)
  • Fixes an issue with Webpack eating a lot of CPU in some cases (@dceddia in #294)
  • We now warn if you import a file with mismatched casing because this breaks the watcher (@alexzherdev in #266)
  • CSS files specifying ?v= after asset filenames, such as Font Awesome, now works correctly (@alexzherdev in #298)
  • Issues with npm linking react-scripts have been fixed (@dallonf in #277)
  • We now use /static prefix for assets both in development and production (@gaearon in #278)

Migrating from 0.2.0 to 0.2.1

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.

0.2.0 (July 28, 2016)

Build Dependency (react-scripts)

  • You can now enable deployment to GitHub Pages by adding homepage field to package.json (@dhruska in #94)
  • Development server now runs on 0.0.0.0 and works with VirtualBox (@JWo1F in #128)
  • Cloud9 and Nitrous online IDEs are now supported (@gaearon in 2fe84e)
  • When 3000 port is taken, we offer to use another port (@chocnut in #101, 2edf21)
  • You can now import CSS files from npm modules (@glennreyes in #105, @breaddevil in #178)
  • fetch and Promise polyfills are now always included (@gaearon in #235)
  • Regenerator runtime is now included if you use ES6 generators (@gaearon in #238)
  • Generated project now contains .gitignore (@npverni in #79, @chibicode in #112)
  • ESLint config is now more compatible with Flow (@gaearon in #261)
  • A stylistic lint rule about method naming has been removed (@mxstbr in #152)
  • A few unobtrusive accessibility lint rules have been added (@evcohen in #175)
  • A .babelrc in parent directory no longer causes an error (@alexzherdev in #236)
  • Files with .json extension are now discovered (@gaearon in a11d6a)
  • Bug fixes from transitive dependencies are included (#126)
  • Linting now works with IDEs if you follow these instructions (@keyanzhang in #149)
  • After building, we now print gzipped bundle size (@lvwrence in #229)

Global CLI (create-react-app)

Migrating from 0.1.0 to 0.2.0

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.

0.1.0 (July 22, 2016)

  • Initial public release