env.js is only for variables injected into the app.

Fixes: #253

tagging dev-only code (@remove-on-publish-begin/end) and pre-eject-only code (@remove-on-eject-begin/end) #257 (#257)

This makes generators work with Jest.

Fixes #255.
Replaces #262.

Disabled because of issues:
 * https://github.com/facebookincubator/create-react-app/issues/525
 * https://phabricator.babeljs.io/search/query/pCNlnC2xzwzx/

TODO: Enable again when these issues are resolved.

* Update Jest

* Remove default snapshot test

* Fix a few things

* Add a simple default test

* App.spec.js -> App.test.js

* Fix e2e test

* Bump Jest

Remove the `include` setting from webpack loaders for CSS, JSON and other static assets.
This way it's possible to import files from a separate config folder, a parent directory etc.

* Started using babel-preset-latest

* Updated babel dependencies

* Remove redundant babel-plugin-syntax-async-functions

* Disabled redundant regenerator transform

This rule is considered dangerous in certain situations. This is especially true for Immutable.js users. See the discussion at issue #465 for more information about this.

* add off font format to loaders

* add otf format support

This will work correctly when there are duplicate filenames in different paths.
Fixes: #445

* Load favicon through html-loader.

Fixes #291.

* Add test for *.ico in e2e test suite

* Configure html-loader to process <link href="...">

* Address feedback on html-loader inclusion.

* Place favicon.ico at the root of the build dir

* Make comment style consistent between prod and dev webpack configs

* Fix html-loader config in dev mode

Disable timer mocking and enable verbose output.

Fixes #377

* Added a reasonable config for autoprefixer (resolves #73)

* Moved autoprefixer config to webpack.config

Fixes #186

* Transform async functions with regenerator

Remove `transform-async-to-generator`, which to my understanding is meant
to be used in environments that support generators natively.

Because we're compiling generators to ES5 anyway, we can simply use
`regenerator` to transform async functions too, which results in
slightly simpler output and only uses the regenerator runtime instead
regenerator runtime + _asyncToGenerator Babel helper.

* Add babel-plugin-transform-regenerator

* Use dependencies with an exact version

* Make Babel config more verbose and simpler

* Support async/await

* Accept version when loading fonts e.g. font-awesome

* Add query string support to mp4/webm

* Use /static paths for assets

* Fix e2e test

* Symlink-friendly path resolution

I was having difficulties using a local copy of `react-scripts` and `npm link`ing it into a real world project. This change resolves paths relative to the current working directory (that is, most likely the directory of the app) rather than assuming a certain directory structure.

* Fix relative paths in post-eject case

because I'm an idiot

* Renamed resolveLib to resolveOwn

This is the one people are converging on, and flow-vars may get deprecated.

This enables us to ship them now, and find a way to resolve runtime path without webpack later.
See https://github.com/facebookincubator/create-react-app/issues/255

Fixes #260