Source and info: https://github.com/facebookincubator/create-react-app
This project uses Nodejs (https://nodejs.org/) (use node -v) to check version.
This installs all the node dependencies for this project. This only needs to be done the very first time this project is downloaded. A "node_modules" folder should now appear in the same folder as package.json.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Serves the pages in the build folder.
Note: this is a one-way operation. Once you eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
Deploys the current built version to gh-pages. This command automatically runs the pre-deploy line in the package.json too.
All the dependencies are safely updated to the wanted version. As well as updating the packages in the node_modules folder, the package.json and package-lock.json files will be updated (use "npm outdated" to find out list of packages). When updating npm or node, ensure travis.yml file has correct version of node