* Use a more sophisticated template for end-to-end testing.
* Not publish integration tests to npm
* Use "commander" for cli argv handling
* Handle different scripts version forms and exits without a name given
* Prepare the commands for testing with a template
* Fix dev "template" path
* Add various features to test
* Test various features separately
* Test language features
* Comment unused e2e.sh lines
* Add "development" tests
* Test environment variables
* Test webpack plugins
* Replace kitchensink README
* Switch integration tests from jest to mocha
* Use `fs-extra`
* Use the correct folders
* Do some cleanup
* Print a better message for `--template`
* Test `npm start` with and without https
* Separate fast e2e testing from kitchensink testing
* Hide `--internal-testing-template` (former `--template`) CLI option
* Update dependencies
* Use published version of eslint-config-react-app for development
We dogfood on our eslint-config-react-app by using it as our ESLint config,
but installing it from the local folder causes problems when its peerDependencies
are updated, because npm won't update it unless the version number changes.
Use the published version for dogfooding so it can be installed from npm.
* Move ESLint configuration to a separate package
* Remove the ESLint configuration, moved to eslint-config-react-app
* Update ESLint instructions
* Pin the package versions in eslint-config-react-app
* Add a README for eslint-config-react-app
* Update README.md
* Update README.md
* Update README.md
* Update README.md
* Update package.json
* Update package.json
* Update production eslint-loader config
* Add the ESLint config to devDependencies of the repo
* 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
* 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
