Added `ws: true` to the httpProxyMiddleware options, and also listen
for the "upgrade" event so that websockets can be proxied immediately,
rather than waiting for an initial HTTP request.

* add logging of existing port process on start

* Move port process wording in start command on to next line

* Color the named processes as cyan in terminal output

* Add handling for multiple processes on a part

- With the currently process filtering, if multiple processes are returned as running on port 3000, this command would fail. This splits apart the process IDing and the process naming, to support multiple processes.
- One curious thing about the bash command to get processes, is that it'll include browsers with a window open on localhost:3000. May want to reconsider that.

* Add process directory to existing port warning

- also moved terminal coloring up, when getting the process, to be able to distinguish the process command from the directory

* Change output color to all cyan, except "in"

* Rename getProcessNameOnPort -> getProcessForPort

- better reflects its broadened scope (both command and directory)

* Add checking if process is a CRA instance, to customize port running message

- moved from using package.json to a regex, for reliability

* Move getProcessForPort to react-dev-utils

- also allowed for breakdown of commands into helper methods

* Add documentation for getProcessForPort

* Add getProcessForPort to list of dev-scripts files

* Use app's package name when CRA app is running on another port

* Filter port process by those listening

- Removed the handling of multiple process IDs since you can filtering by listening process (and not have the browser in the list of processes)
- Trimmed the terminal outputs for better matching (process id) and better terminal output (directory of process)

* Update README on port helpers, to specify only one port returned

* Add ignore of stderr when executing process commands

- Make sure any potential errors don't leak to the user

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.

issue here #762

* Add syntax error overlay in development

* Support HMR being disabled

* Tweak CSS

* Extract some utilities into a separate package

* Add utils dir to `files` in package.json

* Do not create an empty `utils` dir on eject

* Add host as adjustable parameter through env variables

eg: `HOST=test.dev.local npm start`

* Style nit

* Load environment file via dotenv if .env file is present

* Document loading environment variables in .env file

* Minor doc tweaks

* openBrowser() causes docker-compose set ups to fail because of spawn EACCESS - closes #710



Signed-off-by: Aeneas Rekkas (arekkas) <aeneas@ory.am>

* Ignore errors

* Change http-proxy-middleware logLevel from silent to error

* provide onError handler for httpProxyMiddleware

* Send proper error reponse upon proxy error.

* Change http-proxy-middleware logLevel from silent to error

* provide onError handler for httpProxyMiddleware

With the HTTPS env var set 'true', the dev server will serve over HTTPS.

* Disable contentBase in development

* Document #428

tagging dev-only code (@remove-on-publish-begin/end) and pre-eject-only code (@remove-on-eject-begin/end) #257 (#257)

Ref #387

Thanks to @geowarin for the tip in https://github.com/facebookincubator/create-react-app/issues/401#issuecomment-238291901

* Small grammatical correction

* Fix another grammatical error for consistency

This allows users to avoid CORS in simple projects that are hosted on the same server as backend.

Ref: https://twitter.com/sprjrx/status/760481328886272004

Fixes #322

The problem has since been fixed upstream.

This reverts commit f7011e04.

This fixes #302 by temporarily forking `detect-port`.
Hopefully this fix will be merged into the original project, and we can refer to it again.

This seems to work best, both on Windows, OS X, and Linux