In my tests, jsdom was throwing a "SecurityError" at HistoryImpl._sharedPushAndReplaceState (node_modules/react-scripts/node_modules/jsdom/lib/jsdom/living/window/History-impl.js:87:15)

This happens because document.URL defaults to "about:blank". Unfortunately, if you interact with the History object it tries and fails to parse the URL, causing a "SecurityError" to be thrown. Setting the default URL to "http://localhost" fixes this issue.

 - react-scripts@0.8.1

Jest matches moduleNameMapper regexes with module names, not the full
file path, so the negative lookahead doesn’t work for filtering out
JS files, because they can be imported without the extension. So paths
like `lodash.assign` and `../utils/range` were mislabeled as resources
with unknown file extensions because they have a dot in the name.

As a stopgap measure, revert the moduleNameMapper regex added in #1077.

 - create-react-app@1.0.0

 - babel-preset-react-app@2.0.0
 - create-react-app@0.7.0
 - eslint-config-react-app@0.4.0
 - react-dev-utils@0.4.0
 - react-scripts@0.8.0

* Added functionality to crash the build during CI whenever linter warnings are encountered.

* Updated the docs with a description on how to use the build in CI

* Fixed small typo

* Fixed description of build error.

Added `ws: true` to the httpProxyMiddleware options, and also listen
for the "upgrade" event so that websockets can be proxied immediately,
rather than waiting for an initial HTTP request.

* Add a note for OSX users about watchman and jest

Minor additional information on how to solve watchman problems reported in #713 and #1767

* Introduced new Troubleshooting section

Add better explanation how to solve #713 and linked related Issues.

* Tweak wording and add it to TOC

* add logging of existing port process on start

* Move port process wording in start command on to next line

* Color the named processes as cyan in terminal output

* Add handling for multiple processes on a part

- With the currently process filtering, if multiple processes are returned as running on port 3000, this command would fail. This splits apart the process IDing and the process naming, to support multiple processes.
- One curious thing about the bash command to get processes, is that it'll include browsers with a window open on localhost:3000. May want to reconsider that.

* Add process directory to existing port warning

- also moved terminal coloring up, when getting the process, to be able to distinguish the process command from the directory

* Change output color to all cyan, except "in"

* Rename getProcessNameOnPort -> getProcessForPort

- better reflects its broadened scope (both command and directory)

*...

* Enable useBuiltIns option on object-rest-spread

* note polyfill requirement

* Enable useBuiltIns with transform-react-jsx

* Add direct ref to transform-react-jsx

Revert webpack prod config comments to not refer to dev server.

* Replace `scriptPreprocessor` config with `transform`.
* Also remove `moduleFileExtensions` which has been redundant since 16.0
  (`['js', 'json', 'jsx', 'node’]` is the default)

* Remove bundledDependencies
* Change the e2e scripts to use local file dependencies instead of
  bundledDependencies to test the packages

* Adds to docs - deployment with S3/CloudFront

* Tweaks

Loads all files not already handled by other loaders.
Also, switch image loading from file loader to url-loader.

* Added info on using global variables.

See issue #972.

* Fixed typo.

* Moved new section.

* Small tweaks

* Syntax highlighting

* Add Storybook to the user guide

* Add the missing "Snapshot Testing" link.

* Change the title to something nicer

Old title was looks like a marketing pitch. Change it to something looks great.
The new one is: Developing UI Components with React Storybook.

* Mention React Storybook as a third party tool.

* Nits

* Minor changes

Enable sourcemaps in development

* Update css-loader to 0.26.0

* Update the production webpack config

In the `create-react-app` command, try to install packages using Yarn.
If Yarn is not installed, use npm instead.

In `react-scripts`, detect if the project is using Yarn by checking if
a `yarn.lock` file exists. If the project is using Yarn, display all
the instructions with Yarn commands and use Yarn to install packages
in `init` and `eject` scripts.

* Correctly checks site url to tab url in reuse check

* Bring chrome to foreground focused after tab reuse

* Update `babel-plugin-transform-object-rest-spread` to v6.19.0

The `babel-plugin-transform-object-rest-spread` v6.19.0 update will
allow us to remove the `babel-plugin-transform-es2015-destructuring` and
`babel-plugin-transform-es2015-parameters` as the object rest spread
transform will now work standalone and not require additional tranforms

* Remove unnecessary babel transform plugins from babel-preset-react-app

The `babel-plugin-transform-object-rest-spread` v6.19.0 update makes
these plugins unnecessary, as v6.19.0 can be used stand-alone

Explain the usage of react-jsx-source & react-jsx-self

* Update babel-preset-env to 0.0.8

Changes between 0.0.6 and 0.0.8 should be backwards compatible:
https://github.com/babel/babel-preset-env/blob/master/CHANGELOG.md

* Use `node: 'current'` as target for babel-preset-env

This replaces the hand-rolled node version setup with a new feature that
was introduced in babel-preset-env@v0.0.7

https://github.com/babel/babel-preset-env/blob/v0.0.7/CHANGELOG.md