This repository hosts the code for the new website built to replace the old Rutgers Esports website.
The following guide was written by matchaTiff.
- Download Visual Studio Code.
- Download these extensions:
- Babel Javascript
- Prettier - Code Formatter
- Simple React Snippets
- ESLint
- OPTIONAL: Colorize
- Warning. This extension may have issues with the linter.
- Download React:
npm i react.- If you don't have experience with react, start by making your own test app first and experiment with it. Here's a tutorial.
- Clone:
git clone https://github.com/matchaTiff/Rutgers-Esports.git npm inpm run prep(this downloads large files such as videos)npm start
The following steps assume you are a contributor. We are not taking pull requests from developers outside of the Rutgers Esports tech committee at the moment.
- Clone the project if you haven't already.
git clone https://github.com/matchaTiff/Rutgers-Esports.git - Switch to a new branch.
git checkout -b my-awesome-new-feature - Code your cool feature!
- Run and test your feature.
- Stage, commit, and push your files:
git add <changed-files...>
npm run lint
git commit -m "Cool new commit for my cool new feature"
git push origin <my-awesome-new-feature>
gitwill output a link to help you create a new pull request from there.
- This project uses ESLint to maintain and enfore code quality.
- Specifically, this linter extends airbnb's ESLint configuration with some rule adjustments and additions.
- Before you commit code, run ESLint by running
npm run lint. This will ensure that any newly written code matches a set of style rules. huskyandlint-stagedwill prevent you from pushing code with issues by running the linter before allowing you to commit code.
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.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify