* Add a note for OSX users about watchman and jest
Minor additional information on how to solve watchman problems reported in #713 and #1767
* Introduced new Troubleshooting section
Add better explanation how to solve #713 and linked related Issues.
* Tweak wording and add it to TOC
* 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
* Replace `scriptPreprocessor` config with `transform`.
* Also remove `moduleFileExtensions` which has been redundant since 16.0
(`['js', 'json', 'jsx', 'node’]` is the default)
* Add Storybook to the user guide
* Add the missing "Snapshot Testing" link.
* Change the title to something nicer
Old title was looks like a marketing pitch. Change it to something looks great.
The new one is: Developing UI Components with React Storybook.
* Mention React Storybook as a third party tool.
* Nits
* Minor changes
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.
* Update `babel-plugin-transform-object-rest-spread` to v6.19.0
The `babel-plugin-transform-object-rest-spread` v6.19.0 update will
allow us to remove the `babel-plugin-transform-es2015-destructuring` and
`babel-plugin-transform-es2015-parameters` as the object rest spread
transform will now work standalone and not require additional tranforms
* Remove unnecessary babel transform plugins from babel-preset-react-app
The `babel-plugin-transform-object-rest-spread` v6.19.0 update makes
these plugins unnecessary, as v6.19.0 can be used stand-alone
Upgrade `babel-loader` and remove the cache directory configuration
that was added in #620. `babel-loader` now uses the
`./node_modules/.cache/babel-loader` directory by default, so the
custom config is no longer needed.
* Always build before deploying to gh-pages
* Add line to gh-pages deploy docs about CNAME file
* Remove spaces in npm run command for Windows
* Grammar nit
* Minor tweaks
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.
