I want to look into this, but I’m struggling to foresee how I’ll keep up with updates. I don’t have the capacity right now to be building features in two codebases.
What I’m thinking is to hard fork it at maybe Version 6 or Version 7 with a Vite version, and then give the community access to use it as a foundation. At least then there's an example of this, and I can help by suggesting enhancements in the future. Open to discussion 🙌
make it modular. I would skip this ticket in favor of the npm one.
Sam Bowen-Hughes
Team•
Apr 16, 2025
Just a quick note. I’m starting on this next week. Thinking out loud:
I’m planning to create a new GitHub repo, probably called something like RVE-Vite, and convert the entire version-7 branch into a Vite version.
This Vite repo will be something anyone can request access to. I want to avoid confusion with people being invited to two separate repos on sign-up.
The Next.js version will still be the main priority going forward. The Vite version is more of an experiment to see how adoption plays out.
I'll be leaning on feedback to help shape the Vite version into something useful. If you want to get involved, just shout and I’ll look at adding you with write access.
Would love any thoughts on this approach. I get that everyone has a preferred framework, and my goal is to make RVE as inclusive as possible. This feels like a good step in that direction.
Ayayai Dev
•
Mar 19, 2025
not too hard. did it last night, took a couple of hours end to end (without of-course lambda and ssr rendering, which in my opinion should be left to the user to implement).
Sam Bowen-Hughes
Team•
Mar 26, 2025
Awesome!!
Logan Olson
•
Apr 15, 2025
On a scale from 1/10 how difficult was it to transition it from NextJS to Vite?
Sam Bowen-Hughes
Team•
Apr 18, 2025
Incoming…
Sam Bowen-Hughes
Team•
Apr 20, 2025
This has now been completed. There’s a new GitHub repo with Vite-specific code. I’ll be watching this closely to see what kind of feedback and interest it gets. There’s a chance I may fully commit to the Vite version depending on how it goes.
Note: Vite does not come with rendering out of the box.
If you’re interested in accessing the Vite version, send a request to hello@reactvideoeditor.com with your GitHub account.
Jimmy Gozal Benarditi
•
Apr 30, 2025
Hi @Sam Bowen-Hughes — thanks so much for taking the time to put this together! I really appreciate it. I had a couple of thoughts I wanted to share:
I actually stumbled on this update by chance while checking the feature request progress. I’m not sure how many users are aware of it — I don’t think there was an email or announcement about the new repo (but correct me if I’m wrong!).
Since the Vite version won’t be supported long-term, I’d personally rather use the newer Next.js versions and do the extra work to migrate to Vite each time, rather than stick with an older video editor that's built on Vite. Other people might feel the same way and this might impact adoption.
If you're looking to get broader input from users, maybe sending out a survey via email could help? Just a thought! Maybe 90% of your users prefer Next.js and I’m just an outlier :-)
Comments11
Sam Bowen-Hughes
Mar 26, 2025
I want to look into this, but I’m struggling to foresee how I’ll keep up with updates. I don’t have the capacity right now to be building features in two codebases.
What I’m thinking is to hard fork it at maybe Version 6 or Version 7 with a Vite version, and then give the community access to use it as a foundation. At least then there's an example of this, and I can help by suggesting enhancements in the future. Open to discussion 🙌
Ayayai Dev
Mar 27, 2025
https://reactvideoeditor.featurebase.app/p/bulb-convert-rve-components-into-installable-npm-packages/comment/67da1fface28ead76ab56b13
make it modular. I would skip this ticket in favor of the npm one.
Sam Bowen-Hughes
Apr 16, 2025
Just a quick note. I’m starting on this next week. Thinking out loud:
I’m planning to create a new GitHub repo, probably called something like
RVE-Vite, and convert the entireversion-7branch into a Vite version.This Vite repo will be something anyone can request access to. I want to avoid confusion with people being invited to two separate repos on sign-up.
The Next.js version will still be the main priority going forward. The Vite version is more of an experiment to see how adoption plays out.
I'll be leaning on feedback to help shape the Vite version into something useful. If you want to get involved, just shout and I’ll look at adding you with write access.
Would love any thoughts on this approach. I get that everyone has a preferred framework, and my goal is to make RVE as inclusive as possible. This feels like a good step in that direction.
Ayayai Dev
Mar 19, 2025
not too hard. did it last night, took a couple of hours end to end (without of-course lambda and ssr rendering, which in my opinion should be left to the user to implement).
Sam Bowen-Hughes
Mar 26, 2025
Awesome!!
Logan Olson
Apr 15, 2025
On a scale from 1/10 how difficult was it to transition it from NextJS to Vite?
Sam Bowen-Hughes
Apr 18, 2025
Incoming…
Sam Bowen-Hughes
Apr 20, 2025
This has now been completed. There’s a new GitHub repo with Vite-specific code. I’ll be watching this closely to see what kind of feedback and interest it gets. There’s a chance I may fully commit to the Vite version depending on how it goes.
Note: Vite does not come with rendering out of the box.
If you’re interested in accessing the Vite version, send a request to hello@reactvideoeditor.com with your GitHub account.
Jimmy Gozal Benarditi
Apr 30, 2025
Hi @Sam Bowen-Hughes — thanks so much for taking the time to put this together! I really appreciate it. I had a couple of thoughts I wanted to share:
I actually stumbled on this update by chance while checking the feature request progress. I’m not sure how many users are aware of it — I don’t think there was an email or announcement about the new repo (but correct me if I’m wrong!).
Since the Vite version won’t be supported long-term, I’d personally rather use the newer Next.js versions and do the extra work to migrate to Vite each time, rather than stick with an older video editor that's built on Vite. Other people might feel the same way and this might impact adoption.
If you're looking to get broader input from users, maybe sending out a survey via email could help? Just a thought! Maybe 90% of your users prefer Next.js and I’m just an outlier :-)