* run npm 5.4.0 in CI
* run npm cache clean with --force in CI
* use link instead of install
* Update e2e-installs.sh
* Update e2e-kitchensink.sh
* Update e2e-simple.sh
* Bootstrap with Yarn if we can
* Update test scripts
* Check OS and npm concurrency ability
* Windows support
* Update bootstrap.js
* Install yarn before bootstrap
* Added cache clear to e2e scripts
* Install latest yarn on AppVeyor to avoid windows crashing bug in yarn
* Alternative fix for yarn crashing e2e tests on windows machines
* Revert "Fix wrong path expansion in end-to-end test (#2388)"
This reverts commit 2aafaad72d.
* Revert "Suggest just "yarn build" (#2385)"
This reverts commit 70bf12505c.
* Revert "Catch "No tests found" during CI (#2387)"
This reverts commit 5317b3f910.
* ༼ つ ◕_◕ ༽つ 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
* Add appveyor.yml
* Execute mocha directly in e2e test
* Replace e2e process substitution
* Kill nohup node processes after e2e
* Disable known failing Windows test
* Only build master
The `test` command fails with multiple arguments when given a unary operator such as '-e'. Add a function that can test one or more files by looping over all files.
* 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
