Proposal: framework-aware application commands #3107

Today's vp dev, vp build and vp preview are hard-written to run Vite+'s own vite, vite build, and vite preview. Users of meta frameworks like Nuxt have to use nuxt cli to start a dev server.

I propose introducing a framework-aware application commands, configured through a package-level framework API in vite.config.ts:

defineConfig({
  framework: nuxt(),
  fmt: { semi: false },
  /* ... */
})

Inside, nuxt(), it returns the correct command that vp dev should run, like nuxt dev. It would find binaries under project-level .bin, similar to vp exec.

This means Vite+ passes all arguments to the underlying commands themselves. The usage of vp dev would be the same as nuxt dev, vp dev --help also has the same output as nuxt --help.

Framework-specific configuration would remain in the framework‘s own config file. For example, nuxt.config.ts#vite would still be the source of truth for nuxt features. Vite+ would not automatically merge them from vite.config.ts, we may even consider printing warnings for this case.

Alternative: Why not swtich modes by reading nuxt.config.ts automatically

What we hope to do is not simply nuxt support. There are hundreds of active meta frameworks on the market. Relying entirely on Vite+ to handle the logic would be extremely centralized and difficult to maintain. (Even if doing so could reduce the likelihood of AI agents making mistakes)

Why does this matter, and why is this different from raw vite

In my opinion, Vite+ is the entry point of all development process, vp lint, vp check etc. For Nuxt users, vite cli is almost Invisible, because they have their own oxlint cli and may completely skip vite cli command. When developers and agents are already familiar with vp workflow, changing to nuxt or other cli is a significant change in habits.