feat: Migrate from Create React App to Vite#283
Open
juliopavila wants to merge 7 commits intomainfrom
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description:
This PR represents a significant shift from Create React App (CRA) to Vite, following the migration guide. The React team now recommends moving away from CRA to more flexible and efficient alternatives like Vite, particularly for managing large and complex applications.
Key Changes:
Technical Steps:
@vitejs/plugin-react,vite-tsconfig-paths).vite.config.tsfile tailored to our application's needs.index.htmlto the project root and updated script tags for Vite compatibility.package.jsonscripts to use Vite commands.browserslist-to-esbuild.This migration aligns with the latest industry standards and prepares our application for future scalability and improvements.