Skip to content

kens-visuals/react-tailwind-boilerplate

Repository files navigation

Getting Started with React Tailwind Boilerplate

Clone the the repositery using the following command:

git clone git@github.com:kens-visuals/react-tailwind-boilerplate.git

Then install the neccesary dependancies with:

npm i or npm install

After it's done, make sure to go to package.json and change the name of the project to whatever you named your project. Otherwise it will be react-tailwind-boilerplate🙃

Next reset the remote repo

Use the following command to reset the remote repo from mine to yours

git remote set-url <remote_name> <remote_url>

For example: git remote set-url origin https://git-repo/new-repository.git

Then you can try to add-commit-push to see if you connected your remote repo correctly.

Congrats 🎉 you're all set, you're welcome and happy hacking👨🏻‍💻👾


Available Scripts

In the project directory, you can run:

npm start

Runs the app in the development mode.
Open http://localhost:3000 to view it in your browser.

The page will reload when you make changes.
You may also see any lint errors in the console.

npm test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

npm run build

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.

npm run eject

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.