* 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.
* 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
* 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
Use the configured appBuild value in paths.js instead of hard-coding it to 'build'. This is helpful for the ejected case where the appBuild path is changed to another folder name.
* Added functionality to crash the build during CI whenever linter warnings are encountered.
* Updated the docs with a description on how to use the build in CI
* Fixed small typo
* Fixed description of build error.
In the `create-react-app` command, try to install packages using Yarn.
If Yarn is not installed, use npm instead.
In `react-scripts`, detect if the project is using Yarn by checking if
a `yarn.lock` file exists. If the project is using Yarn, display all
the instructions with Yarn commands and use Yarn to install packages
in `init` and `eject` scripts.
