* Update to jest 24
* Add notice about pnpResolver.js
* Formatting
* Fix linting
* Update to jest 24.1.0
* Update jest-pnp-resolver
* Swap create-react-app params in e2e scripts
* Add extraGlobals to supportedKeys
* Bump jest to 24.3.1
* Bump jest to 24.4.0
* Bumb jest to 24.5.0
* Update template dependencies jest to 24.5.0
* Debug failing test
* Remove jest-pnp-resolver
* Remove console.log
* Revert yarn.lock.cached
* Rename production configuration
* Upgrade lint staged
* Merge mode, bail, devtool, and entry
* Merge output settings
* Remove old comment
* Merge some trivial differences
* Disable minimize in development mode
* Only minify html and generate SW in production
* Adjust comment
* Toggle development plugins
* Add missing imports
* Scope settings
* Delete development config
* Use new config file
* Remove unnecessary config import
* Speed up installs with pnp
* Move to a better relative path test
* Continue work on new test organization
* Move mjs test to new enhanced tests
* Move over last legacy test
* Update behavior e2e script
* Add first iteration of instructions to test readme
* Add some more bad instructions
* Split test command into multiple lines
* Use two workers (do not run in band)
* Bump install timeout
* No global pollution
* Fix PnP support via standard run mechanism
* Prevent circular serve command
* Silent yarn execs
* Fix common commands by using a shell
* Run with npx instead of Yarn
* Remove unused scripts
* Wait for localhost and fix script booting with PnP
* Don't pnp locally because links will cause module resolution to whine
* lint-staged is annoying
* Strip Yarn out of execa runs
* Set default license if none specified
* Don't impose worker limit
* Disable pnp for webpack messages
* Add missing dependency
* Disable timeout and rely on Jest
* Only use 2 jest workers
* Add missing dependency
* Caches the Yarn resolution for faster installs
* Adds the yarn.lock.cached file to the publish list
* Removes the copied lockfile when the install fails
* Updates the release checklist
* Run smoke tests with Jest
* Get a unique port for smoke test
* Upgrade verdaccio across the board
* Drop unneeded step
* Try latest instead
* Boot registry in home directory
* Correct config path
* Add mutex
* Test webpack message formatting
* Strip color
* Add browserslist to default
* Disable another broken feature
- [x] Utilize webpack 4 development and production modes
- [x] Upgrade webpack dev server
- [x] Webpack 4 compatible release of thread-loader
- [x] Webpack 4 compatible release of HtmlWebpackPlugin
- [x] Webpack 4 compatible release of SwPrecacheWebpackPlugin
- [x] Webpack 4 compatible release of WebpackManifestPlugin
- [x] Update README
- [x] Update WebpackDevServerUtils
- [x] Update InterpolateHtmlPlugin
- [x] Update ModuleScopePlugin
- [x] Update WatchMissingNodeModulesPlugin
- [x] Move UglifyJS options to webpack 4 optimize
- [x] Move InterpolateHtmlPlugin to make it tapable on HtmlWebpackPlugin
- [x] vendor splitting via splitChunks.splitChunks (https://twitter.com/wSokra/status/969633336732905474)
- [x] long term caching via splitChunks.runtimeChunk (https://twitter.com/wSokra/status/969679223278505985)
- [x] Make sure process.env.NODE_ENV is proxied correctly to `react-error-overlay`
- [x] Implicit webpack.NamedModulesPlugin in dev config as its default in webpack 4
- [x] Disable webpack performance hints as we have our own filesize reporter
- [x] Replace ExtractTextPlugin with MiniCssExtractPlugin
- [x] Switch to css whole file minification via OptimizeCSSAssetsPlugin rather than per module css minification to gain performance
* Automate screencast recordings
* **screencast.js**: Automate screencast.sh, asciinema, svg-term-cli. Removes progress-bar, npm tree data from cast
* **screencast.sh**: Simulate user input, trigger demoed commands
* **screencast-start.js**: Start a shell command and end the process log patterns have been observed
* Run real scripts in local development
* Add preflight check warning
* I know what I am doing
* Move preflight check into individual scripts
This ensures we don't try to filter NODE_PATH twice, accidentally removing the now-absolute path.
* Slightly tweak the wording
* Fix lint
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
