This development starter template is the ultimate solution to help you getting started on your project in no time, without the hassle of setting up and configuring your development environment from scratch each time you start working.
This repository is ideal for front-end developers who want to build modern, fast and reliable webgl web applications with the latest cutting edge technologies such as Three.js, GLSL, JavaScript, TailwindCSS 4, Vite, ESLint, Prettier, Husky and much more!
Demo | Bug(label: bug) | Feature(label: enhancement)
-
Get the repository
- click "Use this template" or "Fork" button
alternately - clone the repository through your terminal:
git clone https://github.com/doinel1a/vite-three-js YOUR-PROJECT-NAME
- click "Use this template" or "Fork" button
-
Decide which package manager you want to use, then delete the unused ".lock" file(s)
-
Open your terminal or code editor to the path your project is located, and run:
npm bun pnpm yarn install dependencies npm installbun installpnpm installyarn installrun the development server npm run devbun run devpnpm devyarn devbuild your production app npm run buildbun run buildpnpm buildyarn buildpreview your production app npm run previewbun run previewpnpm previewyarn preview
This repository comes 🔋 packed with:
- Three.js
- TailwindCSS 4
- Vite
- SASS & SCSS
- ESLint
- Prettier
- Husky
- Commitlint
- Lint staged
- Playwright
The configuration achieves 92.3% coverage across all major browsers, specifically including:
| Chrome | Firefox | Edge | Opera | Safari |
|---|---|---|---|---|
![]() |
![]() |
![]() |
![]() |
![]() |
* In order to support a wider percentage of browsers, update the .browserslistrc configuration file:
last 3 versions: browser version> 0.2%: browser usage statisticsnot dead: whether the browser is officially supported
Update the configuration here and check in real-time the global browsers support.
* The more versions you need to support, the larger the JS and CSS bundle sizes will be.
Contributions are what make the open source community such an amazing place to learn, inspire, and create.
Any contribution is greatly appreciated: big or small, it can be documentation updates, adding new features or something bigger.
Please check the contributing guide for details on how to help out and keep in mind that all commits must follow the conventional commit format.
- Get started
- For a new feature
- Create a new branch:
git checkout -b feat/NEW-FEATURE - Add your changes to the staging area:
git add PATH/TO/FILENAME.EXTENSION - Commit your changes:
git commit -m "feat: NEW FEATURE" - Push your new branch:
git push origin feat/NEW-FEATURE
- Create a new branch:
- For a bug fix
- Create a new branch:
git checkout -b fix/BUG-FIX - Add your changes to the staging area:
git add PATH/TO/FILENAME.EXTENSION - Commit your changes:
git commit -m "fix: BUG FIX" - Push your new branch:
git push origin fix/BUG-FIX
- Create a new branch:
- Open a new pull request
All logos and trademarks are the property of their respective owners.
Everything else is distributed under the MIT License.
See the LICENSE file for more informations.
Special thanks to:
- alrra for browser-logos
- tandpfun for skill-icons




