Skip to content
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

[Feat] Migrate CRA to Vite for Improved Performance #162

Open
dimassibassem opened this issue Aug 31, 2023 · 1 comment
Open

[Feat] Migrate CRA to Vite for Improved Performance #162

dimassibassem opened this issue Aug 31, 2023 · 1 comment
Labels
wontfix This will not be worked on

Comments

@dimassibassem
Copy link

Issue Overview:
This issue focuses on migrating our project from Create React App (CRA) to Vite, aiming for enhanced build performance and a smoother developer experience.

Benefits:

  1. Faster build times with Vite's optimized dependency graph.
  2. Real-time updates via Instantaneous Hot Module Replacement (HMR).
  3. Streamlined configuration and efficient bundling.

Tasks:

  1. Evaluate compatibility and plan migration strategy.
  2. Set up Vite environment and configurations.
  3. Migrate code incrementally while ensuring compatibility.
  4. Update dependencies for Vite integration.
  5. Test build performance and runtime responsiveness.
  6. Ensure HMR and smooth local development workflow.
  7. Update documentation to reflect changes.

Desired Outcome:
This migration to Vite should result in quicker builds and a more efficient development process. Assigning this issue to myself to lead the migration effort. Looking forward to the benefits Vite brings to the project.

@dimassibassem dimassibassem changed the title [Feat]Assign to Me: Migrate CRA to Vite for Improved Performance [Feat] Migrate CRA to Vite for Improved Performance Aug 31, 2023
@gbowne1
Copy link
Owner

gbowne1 commented Aug 31, 2023

@dimassibassem

This is great idea and I agree, however we are not going to focus on this update at this point in time., it's too large of a scope for only a few developers.

If and when we do this in the future, the stack will include:

NextJS or Vite
Vitest
Typescript
MongoDB w/Mongoose
Prisma
TailwindCSS
MUI/Material UI
Redux or Redis

and I would rather do everything at once instead of piece by piece anyhow.

This was discussed here: #132 and you are more than welcome to discuss this there. This sort of high level change (a lot of changes) should be discussed as a group/community and a decision must be made with everyone working on the project.

@gbowne1 gbowne1 added the wontfix This will not be worked on label Aug 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants