-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(doop): migrate to vite/vitest #464
Conversation
|
|
the classic, new line |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job, have few comments left!
Summary
This PR replaces esbuild with Vite and Jest with Vitest, unifying the build and testing processes across the project. This transition eliminates many dependencies, such as Babel, resulting in a leaner setup while preparing the codebase for future TypeScript integration.
With Vite, we gain the ability to generate static builds that can easily be deployed to platforms like GitHub Pages. Vite uses an index.html file located in the project’s root as the entry point, then generates a final index.html with all asset references dynamically replaced by URLs pointing to the optimized, generated assets.
A key advantage of Vite is that it supports this static build workflow even during development, meaning you can preview the final production-like setup with live-reloading and asset management in real-time, streamlining the development process and improving efficiency.
Related Issues
Screenshots (if applicable)
Testing Instructions
npm i
npm run TASK
Checklist