Allow disabling dlx function globally with vpx

Aperta
  • Qualcosa non va?
#2,880 5 commenti 3 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@BlankParticle ci sta già lavorando.

Dal 5/10/2026.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
48/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
cli

Direzione di ricerca

Start by locating the vpx binary-resolution path in the CLI crate — the point where a missing local binary falls back to downloading from npm and executing. The config schema needs the new vpxDlxBehaviour option (allow/ask/deny), with non-interactive environments treating ask as deny, while vp dlx keeps its current behaviour. Read CONTRIBUTING.md for build and test steps; done means vpx cowsay prints the suggested message under deny and existing dlx tests still pass.

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

Descrizione

contribution welcome enhancement
Description

Basically same as what Nub does https://x.com/colinhacks/status/2099827579817779683
When the config is set, if the current project doesn't have the bin installed and the user tries to do vpx <something>, don't try to download it from npm and execute

Suggested solution

there can be option like vpxDlxBehaviour = allow(default) | ask | deny which will figure out what needs to be done when vpx is invoked with a not installed package, in non interactive envs like for agents, ask will deny, vp dlx will still work, but its a more conscious choice which is saying download and execute this from npm

$ vpx cowsay

`cowsay` is not a installed binary in this project, if you meant to execute `cowsay` from npm, use `vp dlx cowsay`
Alternative

Hope you don't typo the package name or use the wrong binary name,
I have done it most with typescript, where I don't have typescript installed, I try to do vpx tsc which resolves to tsc on npm (which is a placeholder that warns about this exact thing)

Additional context

No response

Validations
  • Read the Contributing Guidelines.
  • Confirm this request is for Vite+ itself and not for Vite, Vitest, tsdown, Rolldown, or Oxc.
  • Check that there isn't already an issue requesting the same feature.
Lingua principale
TypeScript
Stelle
6.6k
Fork
303
Merge medio
1g 5h
PR unite (30g)
212

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 TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.