Please run npm i before running any of the npm run commands.
To keep ourselves organized, I made 2 branches dev and main.
devwill be our development branch. This is where our ongoing changes will go to.mainis meant for stable releases. This is so we can easily rollback to a working version in case we break something horribly
Furthermore, make your local changes to a separate local branch on your system. It could be whatever you want to call it like:
branch/your-name So mine would be branch/nathaniel for example.
Either way, you won't have to push this branch to the github repo. This branch will stay locally on your device.
Think of this as your local dev branch.
Please do this so that we dont (potentially) experience multiple conflicts when we all try to push our changes.
Very simple procedure:
git pull --all
git switch your-local-branch
git rebase dev
*If needed you can run git fetch --all to grab all remote branches before git pull
Why this? It'll keep the overall commit history of the project clean.
git switch dev
git merge your-local-branch
Conflicts may still be possible, resolve them the best you can.
This project was bootstrapped with Create React App.
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.
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.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.