Skip to content

✨ [Feature request]: Migrate from CRA to Vite #1193

Closed as not planned
Closed as not planned

Description

@ammaaraslam

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.

Describe alternatives you've considered.

Screenshot / Screenshare

No response

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Activity

  1. self-assigned this
    on Jun 24, 2023
  2. github-actions commented on Jun 24, 2023

    @github-actions

    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.

  3. positiveabhii commented on Jun 28, 2023

    @positiveabhii

    can I work on this?

  4. ammaaraslam commented on Jun 28, 2023

    @ammaaraslam
    MemberAuthor

    can I work on this?

    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 🙏

  5. positiveabhii commented on Jun 28, 2023

    @positiveabhii

    no worries

  6. linked a pull request that will close this issueCra to vite #1200on Jul 2, 2023
  7. github-actions commented on Jul 28, 2023

    @github-actions

    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!

  8. reopened this on Sep 7, 2023
  9. github-actions commented on Oct 7, 2023

    @github-actions

    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!

  10. reopened this on Oct 4, 2025
  11. tejaskh3 commented on Oct 4, 2025

    @tejaskh3

    Talked to @atapas and picking this up!

  12. priyankarpal commented on Oct 4, 2025

    @priyankarpal
    Member

    Talked to @atapas and picking this up!

    ok, what if we can migrate to nextjs?

  13. atapas commented on Oct 4, 2025

    @atapas
    Member

    Talked to @atapas and picking this up!

    ok, what if we can migrate to nextjs?

    Let's move to vite first

  14. priyankarpal commented on Oct 4, 2025

    @priyankarpal
    Member

    Talked to @atapas and picking this up!

    ok, what if we can migrate to nextjs?

    Let's move to vite first

    ok then

  15. github-actions commented on Nov 4, 2025

    @github-actions

    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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions