* Run yarn after ejecting.
* On eject, choose to run yarn instead of npm if yarn is available.
* Move monorepo to react-dev-utils.
* Fix lint.
* Rename monorepo to workspaceUtils.
* Add react-dev-utils dep for create-react-app.
* getMonorepo -> findMonorepo
* change link to advanced deployment
* Use custom CRA link for deployment
* use custom link for minification failure
* update link for deployment
* feedback
* Offer to set browser defaults
* Catch error on no
* Add ending newlines
* Ensure we re-check to prevent defaults from leaking
* Reduce nesting
* Add defaults message
* More explicit
* 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
* 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.
* 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
* 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
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.
