Array.forEach is passed the following parameters:
currentValue
The current element being processed in the array.
index
The index of the current element being processed in the array.
array
- https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/forEach
console.log takes multiple arguments. We only want to print the first one, the actually message.
Use a 'BROWSER' environment variable with npm start to specify which
browser to open. if the value of 'BROWSER' is not valid executable file,
don't open any browser.
- Use “Chrome” instead of "Google Chrome", It will try to use current active browser.
otherwise, use default.
- If “Chrome”s aren’t running, will fallback to opn(url)
* Reuse empty tab on open chrome apple script
* Break find tab into function
* Use property to store found
* Fix minor issues that caused window to not get active
* Don't strip stack traces of evaluated webpack code
* Strip stack traces at the end of a string
because the last line doesn't always have a `\n` and `create-react-app` is leaving the last line of the stack traces present in the error messages
* code comment
* code comment
* 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
Running `create-react-app` in a Docker container causes an unhandled rejection error in nodejs > 6.5 because the `opn` module tries to open a web browser in a system that doesn't have one. I figured this error could be safely ignored.
A previous commit renamed the apple script to open chrome from
`chrome.applescript` to `openChrome.applescript`. That created
a minor bug. Even when chrome was open with the client app,
`npm start` would open the client app in a new Safari tab on
macOS instead of re-using the open tab in chrome.
