-
-
Notifications
You must be signed in to change notification settings - Fork 841
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
Cra to vite #1200
Cra to vite #1200
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
❌ Deploy Preview for reactplayio failed.
|
Will start testing from tomorrow. I've a question @ammaaraslam Do you see improvement in developer experience in installing dependencies and running the local server? |
@atapas |
@ammaaraslam We need to test the features. Have you started your sanity? |
@ammaaraslam the build fails with these.. please check. Aany build step to change? 7:13:08 PM: node_modules/@mui/system/GlobalStyles/GlobalStyles.d.ts(9,121): error TS2694: Namespace 'React' has no exported member 'JSX'. |
We have merged a few PRs ... could you please pull the latest and do a sanity and let me know? I will rest of the merges until this is merged. Also, consider any other doc changes. |
There hasn't been any activity on this pull request recently, and in order to prioritize active work, it has been marked as stale. This PR will be closed and locked in 7 days if no further activity occurs. Thank you for your contributions! |
Hi @atapas reactplay/create-react-play#41 to don't get problem with creating play in vite as for the moment, plays are still created with .js extension. |
Hi @ammaaraslam I need an update on this. Is it ready to merge? We need to plan further things accordingly. |
There hasn't been any activity on this pull request recently, and in order to prioritize active work, it has been marked as stale. This PR will be closed and locked in 7 days if no further activity occurs. Thank you for your contributions! |
Description
This pull request encompasses the migration of the entire project from Create React App (CRA) to Vite. The migration was performed to leverage the benefits and improvements offered by Vite, aiming to enhance the development experience and improve overall performance.
Project Setup:
The project setup was updated to utilize Vite's build tooling and development server. The existing dependencies and configurations related to CRA were replaced with the corresponding Vite dependencies and configurations.
Build System:
The existing CRA build system based on webpack was replaced with Vite's native build system, which relies on the esbuild bundler. This change streamlines the build process, resulting in faster builds and optimized production bundles.
Development Server:
The CRA development server was replaced with Vite's fast development server, powered by esbuild. The new development server supports hot module replacement (HMR) and provides faster reloading and an improved developer experience.
Configuration:
The project's configuration files were updated to align with Vite's configuration structure. The "vite.config.js" file was introduced to specify custom build settings, plugins, and aliases.
Comparisons:
Changes to be made in terms of documentation and code in other repos:
jsx
elements within it, must be either of.jsx
,.ts
or.tsx
file exension.create-react-play
cli to make sure that future plays are created as either.jsx
,.ts
or.tsx
(Issue has been created here #38 )Fixes #1193
Type of change
How Has This Been Tested?
Tested locally. Both building the app and running Cypress tests.
Checklist: