feat: Add comprehensive Vinext framework support throughout codebase

[Alisha-21-cloud]

This pull request adds comprehensive support for the new vinext frontend option throughout the CLI codebase. The changes ensure that vinext is treated similarly to next (Next.js) in compatibility checks, prompts, UI library defaults, and documentation. Additionally, a minor lint rule adjustment is made.

Key changes include:

Vinext Frontend Support

• Added vinext as a recognized frontend option in prompts, compatibility checks, and error messages. This includes updating arrays, prompt options, and user-facing guidance to mention or include vinext wherever next (Next.js) is referenced. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13]

• Updated compatibility constants and mappings to include vinext as a supported frontend for addons and UI libraries, ensuring it is available wherever next is supported. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12]

• Updated helper functions and logic to recognize vinext as a React-based frontend and to handle it in setup and recommendation flows, such as for addons and devtools. [1] [2] [3]

Closes #162

This pull request adds comprehensive support for the new vinext frontend option throughout the CLI codebase...

[vercel]

@Alisha-21-cloud is attempting to deploy a commit to the Ibrahim's projects Team on Vercel.

A member of the Team first needs to authorize it.

[moneymastersaa-collab]

🎉 This is exactly what I was hoping for!

Hey @Alisha-21-cloud — thank you so much for picking this up and implementing it so thoroughly. As the one who opened issue #162, I can say this PR goes well beyond what I had in mind, and in the best way possible.

What stood out to me

The coverage is remarkably complete. Rather than a partial or shallow integration, vinext has been wired through every layer of the CLI — prompts, compatibility constants, UI library mappings, addon setup, MCP guidance, auth validators, and error messages. That kind of consistency is really hard to achieve and means I won't hit surprising edge cases when actually using it.

The UI library defaults make sense. Defaulting vinext to shadcn-ui (same as next) is the right call — it reflects that Vinext projects are still fundamentally React/Next.js at their core, just with Vite's compiler powering them.

Auth provider support is well thought out. Seeing that nextauth, stack-auth, supabase-auth, auth0, and clerk all explicitly support vinext is huge. Auth configuration is one of the most painful parts of bootstrapping a project, and having these work out of the box is exactly the kind of thing I needed.

The MCP guidance and ambiguity rules are a nice touch. Adding "When the user says 'fullstack Vinext', use backend='self', frontend=['vinext'], runtime='none'" to the ambiguity rules means the AI-assisted scaffolding path works correctly too — that level of attention to detail is appreciated.

The actual template files are included. The packages/template-generator/templates/frontend/react/vinext/ directory with package.json.hbs, vite.config.ts.hbs, layout.tsx.hbs, and the rest gives me everything I need to scaffold a real project. This was literally the ask in my original issue.

The docker-compose and Tauri templates are updated too. Those are addons I plan to use alongside Vinext, so seeing them accounted for is a relief.

Overall

This is a well-scoped, well-executed contribution. The changes are systematic, the test files are updated in parallel, and the diff is clean. I'm genuinely excited to try this out once it lands.

Thanks again for taking the time — this is a great addition to the project. 🙏

[moneymastersaa-collab]

👋 Hey @Marve10s — would love your review on this one!

Just wanted to flag this PR directly to you since it closes issue #162 which I opened a while back requesting a Vinext (Vite + Next.js) template.

@Alisha-21-cloud has done a really thorough job here — the implementation touches every relevant layer of the codebase (prompts, compatibility rules, UI library mappings, auth validators, MCP guidance, and the actual template files themselves), so this isn't a surface-level addition at all.

From my perspective as the issue opener, this PR delivers exactly what was requested and then some. I've gone through the diff and everything looks consistent and well thought out.

When you get a chance, could you take a look and consider merging this in? Would mean a lot to have Vinext as a first-class option in Better-Fullstack — it's a setup a lot of people are reaching for these days and having it available via the CLI would save a ton of manual scaffolding time.

No rush of course, just wanted to make sure it was on your radar. Thanks for maintaining such a great project! 🙏

[Marve10s]

👋 Hey @Marve10s — would love your review on this one!

Just wanted to flag this PR directly to you since it closes issue #162 which I opened a while back requesting a Vinext (Vite + Next.js) template.

@Alisha-21-cloud has done a really thorough job here — the implementation touches every relevant layer of the codebase (prompts, compatibility rules, UI library mappings, auth validators, MCP guidance, and the actual template files themselves), so this isn't a surface-level addition at all.

From my perspective as the issue opener, this PR delivers exactly what was requested and then some. I've gone through the diff and everything looks consistent and well thought out.

When you get a chance, could you take a look and consider merging this in? Would mean a lot to have Vinext as a first-class option in Better-Fullstack — it's a setup a lot of people are reaching for these days and having it available via the CLI would save a ton of manual scaffolding time.

No rush of course, just wanted to make sure it was on your radar. Thanks for maintaining such a great project! 🙏

@Alisha-21-cloud Can you please fix the CI failure?

[Alisha-21-cloud]

@Alisha-21-cloud Can you please fix the CI failure?

Hey @Marve10s! 👋

Just a quick update on PR:

• ✅ Release Guard — fixed
• ✅ Lint — fixed
• 🔧 Test (create-better-fullstack#test) — working on it, will push a fix soon

Will update once the test job is green!

[Marve10s]

@Alisha-21-cloud Can you please fix the CI failure?

Hey @Marve10s! 👋

Just a quick update on PR:

* ✅ **Release Guard** — fixed

* ✅ **Lint** — fixed

* 🔧 **Test** (`create-better-fullstack#test`) — working on it, will push a fix soon

Will update once the test job is green!

No need to write message, I can see notification about every commit. And please try to just translate your messages if you don't speak English, AI makes text much worse and soulless