mirror of
https://github.com/cloudflare/vinext.git
synced 2026-05-09 08:25:34 +02:00
[GH-ISSUE #21] How serious is this project? #9
Labels
No labels
enhancement
enhancement
good first issue
help wanted
nextjs-tracking
nextjs-tracking
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vinext#9
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @switz on GitHub (Feb 24, 2026).
Original GitHub issue: https://github.com/cloudflare/vinext/issues/21
I'm just curious how serious this project is. Is it just an experiment? Is it an experiment... until it's not? Or maybe it's just a serious experiment?
I guess what I'm wondering is: is cloudflare genuinely investing in this project for the next 3+ months? If so, is there a way to join a discussion on its roadmap?
While building on next.js' APIs is a strong start, there are several patterns that next.js struggles with (mostly around the deep commitment to streaming. e.g. status codes, proper middleware, over-parallelization) that I think would be more interesting to pursue if given different design decisions early on.
If this is intended to be a serious alternative one day, it would make sense to start from first principals and identify the fatiguing parts of next.js, while bringing forth a better ux and dx.
Nice work! Glad to see alternative adoption towards react server components!
@eglove commented on GitHub (Feb 25, 2026):
I don't really get this tbh. Vibe coding a copy. Funny... but doesn't seem worth an announcement. TanStack Start is compatible. Angular SSR is sort of compatible, albeit I've never had a successful deployment due to deprecated node APIs... Why not work with making sure these work?
@southpolesteve commented on GitHub (Feb 25, 2026):
Great questions, thanks for taking the time to ask and check out the project.
First, I'd point you to the FAQ in the README which covers some of this, but I'll expand on it.
What I said in the blog post is real: this genuinely started a week ago. It very much began as an experiment, and like many serious things, quickly grew into something more. Based on the response we've gotten, and the fact that we've already seen it work in production for some customers, we are definitely going to be investing in this.
I can say that with some authority. Yes, I'm the one who wrote most of this project, but I'm also the director in charge of the entire Cloudflare Workers org, almost 80+ people at this point. I'm not just an IC engineer who has to find time to justify continuing to work on this. I can literally put people on it, and I've already been talking to the team about how to do exactly that.
As far as Next.js's APIs: the current goal is to maintain parity with Next. I've definitely heard from people that there are things about Next they don't like, and I appreciate that perspective. But right now, diverging significantly from Next's API surface isn't really in scope. Obiviously we already me an exception with TPR, which is an alternative take on pre-rendering, but the bulk of the Next.js APIs we're trying to match 1:1. The reason is straightforward: we're trying to give customers who are having a hard time hosting Next on Cloudflare a better time.
The last thing I'll say is this: if I could create a copy of Next in a week using only AI, you could probably build a framework that mirrors Next in the ways you like and solves the problems you're describing in even less time. Honestly you should just try. The hard parts of framework development has gotten a lot easier.
We're going to see where this project goes, what kind of feedback we get, and figure out where to take it from there. Hopefully that answers some of your questions.
@eglove commented on GitHub (Feb 25, 2026):
I don't know why honest conversation is being marked as spam. My advice to everyone is to not take this seriously. A vibe coded copy is essentially a fork. And if you've been around long enough you've seen the Next forks come and go.
Cloudflare as a platform could do with better support for the frameworks that currently list as supported. (Is this why my comment was deleted?)
Or with a framework built to really take advantage of the runtime.
I don't think we need another node framework when TanStack Start is already out there.
@tannerlinsley commented on GitHub (Feb 25, 2026):
I’m flattered to see the FanStack out in full force, but I’d love to add my 2 cents that it’s definitely unrealistic to expect a vast majority of Next users to migrate to Start with the same level of ease that is being offered here. Obviously I would love that, and we plan on enticing people with great features and performance that they’ll want to do that anyway, but if they can, in the interim, run an agent skill and essentially gain perf/compatibility in a literal hot minute, I say go for it. In my experience, Cloudflare doesn’t mess around. I know Steve, and I fully expect this library and its maintainers to continue to take it seriously as probably the first actual viable next “fork” since opennext, but even that’s being very loose with the term.
Great work guys :)
@southpolesteve commented on GitHub (Feb 25, 2026):
Thanks @tannerlinsley for chiming in! To be clear we would also love to see more people migrating to tanstack too! Big fans over here. I've seen what LLMs are capable of with this project and "migrate me to tanstack" is definitely something they can handle.