Since yarn.lock shouldn't be added to the repo, nor excluded via
.gitignore, lets take advantage of lint-staged to remove any staged
yarn.lock files before they can even be committed.
* Bootstrap with Yarn if we can
* Update test scripts
* Check OS and npm concurrency ability
* Windows support
* Update bootstrap.js
* Install yarn before bootstrap
* Local testing with docker
* Docs on e2e testing
* `bash` callback after docker
* Add a TL;DR in the CONTRIBUTING section
* Local e2e testing with modified files
* Remove the N.B. from the README
* Fixed a fixme in e2e doc
* ༼ つ ◕_◕ ༽つ stack-frame-overlay
* Fix linting
* Remove auto overlay
* Fix e2e
* Pull in the rest
* Appease flow
* Correct dep
* Remove old repo references
* Check flow on test
* Test overlay in e2e
* Add cross env
* Rename package
* Make sure it gets built post-install
* Update the README
* Remove extra builds now that there's a postinstall script
* Revert "Remove extra builds now that there's a postinstall script"
This reverts commit 8bf601dbd36c1e0da7f785fa9ade70ab08ed8772.
* Remove broken script
* Fix some dev ergo
* mv create-react-app/index.js -> create-react-app/creteReactApp.js
* update to modern code style
* var -> cosnt
* set trailing-coma to es5 for prettier
* updating eslint to 3.16.1
* add support for ignoreRestSiblings in eslint
http://eslint.org/docs/rules/no-unused-vars#ignorerestsiblings
* updating eslint to 3.16.1 in `react-scripts`
* updating eslint
* missing `^`
* missing ^
* pinning main eslint and updating readme
* Pin ESLint version
* Disable require.ensure
* Replace require.ensure with import
* Add babel plugin for parsing import()
* Get the default
* Upgrade babel-eslint to support dynamic import
* Fix dep
* Update deps
* 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
