* Use latest npm in e2e tests

* Keep default npm version in "simple" test

* Try to fix CI by using a version that supports Yarn

* add link to deployment docs after build

* Update printHostingInstructions.js

* Lint against files with old license

* Update e2e-simple.sh

* Update e2e-simple.sh

* oh no

* Use proxy for all request methods other than GET

* Add comment

* Replacing literal 'build' with `buildFolder` variable

* Cleaning up the printHostingInstructions a bit

* Fixing undefined variable

* Added documentation for contributors using windows 10

Hopefully encourages devs on Windows machine to contribute

* corrected the wordings a little

* Port cra.sh development task to javascript

* Port cra.sh development task to javascript

Use absolute path when generating .tgz path

* Extend --scripts-version to include .tar.gz format

* Removal of debug console.log

* added getProxy

getProxy checks proxy settings from process.env.https_proxy or Yarn (NPM) config (.npmrc)

* changed yarn for npm to get https-proxy 

default value for https-proxy is null, not undefined like in yarn

awk splits lines based on spaces, which causes directory names with spaces to end up in other fields. Using a for loop allows us to print from the 9th field onwards instead of just the 9th field.

* fix #2223 - [feature] Implement dotenv-expand to accept variable expansion in dot env files

* add to README TOC

* fix readme

* Update README.md

* add envinfo package, —info flag

* update envinfo to use new duplicates option

Added some more documentation to install the babel-preset-react-app making it more clear on how to get started with this preset outside of create-react-app.

It appears trusty has Yarn ^v1.0.0 now.

So (#3054) shouldn’t be an issue changing to trusty. As Travis CI [precise support](https://blog.travis-ci.com/2017-08-31-trusty-as-default-status) will be dropped in March 2018 .

* Allowing for local "file:" prefixed scripts packages

* Fixing test failure

* Open editor to exact column from build error overlay

* Update launch editor validations

* Better documentation for setupTests.js when ejecting

When running `npm run eject` before creating `src/setupTests.js`, the resulting `package.json` file, won't contain any entry for it - and this is correct in my opinion, since otherwise Jest will crash - but it's useful to have it documented and avoid pointless waste of time.

* Added additional note about src/setupTests.js

Added another note about src/setupTests.js and `npm run eject` in Testing Components section

* Update README.md

* Update README.md

* Add svg screencast

* Use svg screencast

'more' and 'simpler' together is incorrect.

If create-react-app project is ejected and webpack configuration is
modified to multi build setup FileSizeReporter would fail.

In those situations `webpackStats` parameter would contain stats array
for each build. This fix will try to access stats and then falls back
to using plaing webpackStats object.

* Update the string that clears the console.

#1914
I've tested it with Windows 10 and 7, node versions from ~5.0.0 up to 7.7.0.
Didn't managed to test it on 8 but it should be fine.

* Update windows string

Add windows specific string for clearing the console.

* add support to set REACT_EDITOR to none

* change README message

* change condition to avoid problems with editor being null

* move condition to avoid extra code

* Update README.md with a note that reminds users to prepend REACT_APP_ to their environment variables. 
* Based on #865, where Dan Abramov suggests the person who filed the issue create a PR with these changes.
* Took the language from [Adding Custom Environment Variables](https://github.com/facebookincubator/create-react-app/tree/master/packages/react-scripts/template#adding-custom-environment-variables)

Fixes #2793