This project was bootstrapped with Create React App.
First steps:
- Clone project by running:
git clone https://github.com/nejcrogelsek/react-project-template.git
- Delete .git file inside cloned project.
- Run:
yarn run start:clean
- Initialize git & run:
yarn run husky:postinstall
to install husky git hook (automatically formats the code when pushing code to github)
With react-location instead of react-router-dom:
- Clone project by running:
git clone https://github.com/nejcrogelsek/react-project-template.git
- Fetch the react-location branch:
git fetch origin feature/react-location
- Checkout into react-location branch:
git checkout feature/react-location
- Delete .git file inside project.
- Run:
yarn run start:clean
- Initialize git & run:
yarn run husky:postinstall
to install husky git hook (automatically formats the code when pushing code to github)
With tailwindCSS & react-location:
- Clone project by running:
git clone https://github.com/nejcrogelsek/react-project-template.git
- Fetch the tailwind react-location branch:
git fetch origin feature/tailwind-react-location
- Checkout into react-location branch:
git checkout feature/tailwind-react-location
- Delete .git file inside project.
- Run:
yarn run start:clean
- Initialize git & run:
yarn run husky:postinstall
to install husky git hook (automatically formats the code when pushing code to github)
In the project directory, you can run:
Remove node_modules
& yarn.lock
& yarn-error.log
files.
Then it runs: yarn
to install all packages & finally yarn start
to run 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.
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.
This command generates new icons. Before running this command make sure you have:
- .svg files inside src/assets/icons
- Run:
yarn generate:icons
- Format file
src/components/shared/Icon/Icon.generated.tsx
to get rid of eslint/prettier errors.
Generates new page with specified name.
Generates new component with specified name.
yarn update:check
- Check for any packages updates.yarn update:single packageName
- Updates one package.yarn update
- Updates all packages.
yarn code:check
- Check for any prettier errors.yarn code:format
- Format code.yarn code:format:specific-file
- Format specific file.
yarn lint
- Check for any eslint errors.yarn lint:fix
- Fix some of the errors.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.