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

`dependsOn` object form cannot reach a task behind a package that lacks it; the query can

Aperta
  • Qualcosa non va?
#738 1 commento 0 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
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
build-system, cli

Direzione di ricerca

Start with task-query.md and the UserDependsOnEntry::Package behavior in vite-task b11dbb9. Reproduce the difference between vp run app#build and vp run -t app#generate on the shown package graph, then trace how skip-intermediate reconnection is implemented. Done means the selected approach reaches transitive generate tasks without duplicate execution and has coverage for packages that lack the task.

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

Descrizione

Problem

{ task, from } selects direct dependencies only, and the docs say recursion comes from each dependency task declaring its own entry. That chain breaks at any package that does not define the task, and every task must have a command, so a source-only package cannot relay.

app ──> ui (no generate) ──> icons (has generate)

app#build: dependsOn: [{ task: 'generate', from: 'dependencies' }]

vp run app#build on a clean checkout never runs icons#generate. vp run -t app#generate does, because the query bridges ui (skip-intermediate reconnection, task-query.md). The two mechanisms disagree about the same package graph.

Why it matters

In a monorepo whose packages are consumed as source, the only per-package preparation is code generation, and only some packages have it (25 of 121 for us). Every consumer task (test, lint, build) needs "generate in everything I transitively depend on". That is a cross-name dependency, so the query cannot express it (-t test would run test everywhere), and nested vp run -t generate is not deduplicated (#323). Today we name far-away producers by hand in a consumer that does not depend on them, keep a hand-written list of every producer for the workspace type build, and run vp run -r generate as a CI pre-pass.

Ask (either)

  1. { task: 'generate', from: 'dependencies', transitive: true }: materialize edges to the task across transitive dependencies through from, bridging packages that lack it, which is the skip-intermediate reconnection the query already implements. task-query.md argues against stored topological edges because package selection is per query; an explicit entry does not vary per query, so that argument does not apply.
  2. Allow a task with dependsOn and no command, so a source-only package can relay. This is Turborepo's documented Transit Nodes pattern (a task that "doesn't do anything because it doesn't match a script in any package.json"). Without it we need command: 'true' in about 100 packages.

Option 1 is the better end state: no relay tasks at all.

Versions: vite-plus 0.3.3; read against vite-task b11dbb9 (UserDependsOnEntry::Package is documented "Direct package dependency selection entry").

Lingua principale
Rust
Stelle
468
Fork
42
Merge medio
1g 18h
PR unite (30g)
46

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-task

Tutte le issue di voidzero-dev/vite-task

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.