You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
✨ [Feature request]: Migrate from CRA to Vite #1193
Is your feature request related to a problem? Please describe.
ReactPlay currently uses CRA as its build tool, which is now considered to be far back from other available tools in terms of performance and its limitations.
Describe the solution you'd like.
To tackle this, migrating the project from using CRA to Vite would address these problems and improve the overall development experience. Vite is much faster, more efficient and provides more tools to improve developer experience.
Hey! contributor, thank you for opening an Issue 🎉.
@reactplay/maintainers will review your submission soon and give you helpful feedback.
If you're interested in continuing your contributions to open source and want to be a part of a welcoming and fantastic community, we invite you to join our ReactPlay Discord Community.
Show your support by starring ⭐ this repository. Thank you and we appreciate your contribution to open source! Stale Marking : After 30 days of inactivity this issue/PR will be marked as stale issue/PR and it will be closed and locked in 7 days if no further activity occurs.
There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a 👍 Because this issue is marked as stale, it will be closed and locked in 7 days if no further activity occurs. Thank you for your contributions!
There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a 👍 Because this issue is marked as stale, it will be closed and locked in 7 days if no further activity occurs. Thank you for your contributions!
There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a 👍 Because this issue is marked as stale, it will be closed and locked in 7 days if no further activity occurs. Thank you for your contributions!
Activity
github-actions commentedon Jun 24, 2023
Hey! contributor, thank you for opening an Issue 🎉.
@reactplay/maintainers will review your submission soon and give you helpful feedback. If you're interested in continuing your contributions to open source and want to be a part of a welcoming and fantastic community, we invite you to join our ReactPlay Discord Community.
Show your support by starring ⭐ this repository. Thank you and we appreciate your contribution to open source!
Stale Marking : After 30 days of inactivity this issue/PR will be marked as stale issue/PR and it will be closed and locked in 7 days if no further activity occurs.
positiveabhii commentedon Jun 28, 2023
can I work on this?
ammaaraslam commentedon Jun 28, 2023
Hey @abhijain1705
Thanks for the interest in it, but we're almost done with the issue.
Please have a look at other open issues.
Thanks 🙏
positiveabhii commentedon Jun 28, 2023
no worries
github-actions commentedon Jul 28, 2023
There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a 👍 Because this issue is marked as stale, it will be closed and locked in 7 days if no further activity occurs. Thank you for your contributions!
github-actions commentedon Oct 7, 2023
There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a 👍 Because this issue is marked as stale, it will be closed and locked in 7 days if no further activity occurs. Thank you for your contributions!
tejaskh3 commentedon Oct 4, 2025
Talked to @atapas and picking this up!
priyankarpal commentedon Oct 4, 2025
ok, what if we can migrate to nextjs?
atapas commentedon Oct 4, 2025
Let's move to vite first
priyankarpal commentedon Oct 4, 2025
ok then
github-actions commentedon Nov 4, 2025
There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a 👍 Because this issue is marked as stale, it will be closed and locked in 7 days if no further activity occurs. Thank you for your contributions!