Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Proposal: framework-aware application commands

Aperta
  • Qualcosa non va?
#3,107 0 commenti 2 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
28/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
nuxt, rust, typescript
Ambito
backend-api-design, cli, tooling

Direzione di ricerca

Start with the vp dev, vp build, and vp preview command-routing entry points and the package-level configuration API used by vite.config.ts. Trace how project-level .bin binaries are currently discovered by vp exec, then define how a framework adapter supplies and receives command arguments. Done means framework commands such as nuxt dev run transparently, including help and passed arguments, while framework configuration remains owned by its own config.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

pending triage

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.

Vite+ command Framework command
vp dev nuxt dev
vp build nuxt build
vp preview nuxt preview

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.

Lingua principale
Rust
Stelle
6.3k
Fork
283
Merge medio
1g 16h
PR unite (30g)
214

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di voidzero-dev/vite-plus

Tutte le issue di voidzero-dev/vite-plus

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.