-
Notifications
You must be signed in to change notification settings - Fork 100
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
Migrate to Vite #171
Comments
We've been having Vite on our Radar, but were hesitant to jump on yet another hype train. But now that they recommend it in React's beta docs (and mention CRA nowhere anymore), I think it's safe to migrate (also, the speed increase is just mind blowing 🤯 ) |
Agreed. Using Vite is way better than CRA. |
Hey @chrstnbwnkl @nilsnolde, While migrating I found some issues that needs to be addressed
For now, I did not remove react-scripts. |
Hello @chrstnbwnkl @samyabrata-maji I am also a react developer and i have migrated my previous project from CRA to Vitejs, I would like to contribute to this project because i think i have the relivent skills. |
Hi @chrstnbwnkl, I would like to help migrate the project to vite. I also have a question regarding the package manager should we use pnpm instead of npm since it will also increase the developer experience substantially. Would like to know your opinion on this. Thanks. |
Description
What kind of feature you are suggesting?
As you know, CRA is slow. I recommend using Vite. Even the official react docs recommend using vite.
Does it solve any problem?
Using Vite would significantly reduce build time, improving developer experience.
It does not have any effect on the production version.
Screenshots
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: