* Fix incorrect check if CI variable is set to true
Originally build would fail on warnings with any value of CI environment variable. Now it will correctly check if it's true.
Discussed here: https://github.com/facebookincubator/create-react-app/issues/2453
* Check for "not false" instead of "not true"
After discussion we decided that this will be closer to current functionality and not break anything.
* Ejecting should ensure you have clean git status
* Rename function
* Style
* Minor changes
- extract function
- exclude error output for missing git
- more descriptive error message
- no need to mutate answer
- fix answering "no" to return 0 exit code
* Override Jest config collectCoverageFrom with package.json
* Protect against overriding other options
* Better error message
* Create Jest config early on eject
* Tweak wording
* Dry it up
* Only run tests in <rootDir>/src (#544)
* updates Jest to 19.0.2
* removes testPathIgnorePatterns from jest config
* adds testMatch to jest config to only match files in src
* Bump babel-jest to 19.0.0 to match jest 19.0.2
* Change proxy handling to allow multiple proxies to be specified in package.json.
* Up webpack-dev-server to 2.4.2
Webpack Dev Server version 2.4.2 handles the external websocket upgrade
for all proxies
* Fix the listen() call
* Switch to correct default host
* Remove promises and extract to react-dev-utils
* oops
* support different env configs.
* fomrat code
* Hide doc
* Slightly rework the PR
* Remove .env in default template
* Use just one entry in the paths
* Unify env.js and loadEnv.js
* Oops, forgot these folks
* Change proxy localhost to I27.0.0.1 for windows
* Update comment
* resolve localhost IP with DNS lookup on windows
* Fix CI errors
* Promisify addWebpackMiddleware
* Remove Node 6 syntax
* Update addWebpackMiddleware.js
* Actually use the resolved proxy
Pass the host from environment variable as argument of the devServer's
listen function instead of a field of options object.
Set the default host to 0.0.0.0 instead of localhost.
* Fix for issue #1798: Suggested 'yarn build' versus 'yarn run build'
* remove 'run' from 'yarn test' command as well
* conditionally show 'run' if Yarn is not available
* Suggest `serve` for serving the `build` directory
* How to handle it with Node in prod (or other platforms)
* Pretty newline added
* Adjusted default port of static server
* Remove `open` command from output
* Removed constant assignment
* Better explanation for not using having to use a static server
* Cute newline added
* Style nits
* 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
* Read script names from own bin instead of guessing
This fixes ejecting from a fork that uses a different bin script name.
* Fix ejecting for a scoped react-scripts fork
We shouldn't hardcode react-scripts because fork name might differ.
We also shouldn't rely on it being an immediate child because scoped packages are a level deeper.
* Clarify that own* properties only exist before ejecting
* Refactor start script into modules
* Move dev server config into config file
* Replace eject file whitelist with a "remove-file-on-eject" flag
* Move utils into scripts folder (for inclusion in ejection)
* Add missed changes
* Pass showInstructions as an argument
* Fix eject bug
* Don't eject babelTransform
