vp treats a nested project as part of the parent's pnpm workspace, ignoring its own packageManager and lockfile
Los mantenedores suelen responder en 1 día
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Describe the bug
In a repo whose root is a pnpm project with a settings-only pnpm-workspace.yaml (no packages, used for overrides / allowBuilds), vp treats every nested project as part of that workspace, even when the nested folder isn't listed under packages and has its own packageManager pin and lockfile.
Inside the nested npm project svc/:
vpr helloruns the root'shelloscript instead of svc's.vp install --frozen-lockfileruns pnpm, which refuses withThis project is configured to use npm. Without apackageManagerfield insvc/it fails withHeadless installation requires a pnpm-lock.yaml fileinstead.vp env currentinsidesvc/reports pnpm 12.11.2 with sourcepackageManager, the root's pin, not svc's[email protected].
I expected vp to treat svc/ as its own npm project, as it does when the root has no pnpm-workspace.yaml. pnpm 11+ only reads settings like overrides from pnpm-workspace.yaml, so a pnpm root can't avoid having one.
We hit this when switching a repo root to pnpm: about 20 Cloud Run services below it stay on npm or bun, and vp stopped working in all of them.
Workaround: a comment-only pnpm-workspace.yaml plus the packageManager pin in each nested project makes vp treat it as its own project again.
Reproduction
https://github.com/Goobles/vp-nested-workspace-repro
Steps to reproduce
git clone https://github.com/Goobles/vp-nested-workspace-repro
cd vp-nested-workspace-repro
./repro.sh
repro.sh runs vpr hello and vp install --frozen-lockfile in svc/, first with the root pnpm-workspace.yaml (bug), then with it moved away (expected behaviour).
System Info
# vp env current (run inside svc/)
Node.js:
Version 24.19.0
Source default
Bin Path /home/agent/.vite-plus/js_runtime/node/24.19.0/bin/node
Installed true
Mode managed
Package Manager:
Name pnpm
Version 12.11.2
Source packageManager
Bin Paths
pnpm /home/agent/.vite-plus/package_manager/pnpm/12.11.2/pnpm/bin/pnpm
pnpx /home/agent/.vite-plus/package_manager/pnpm/12.11.2/pnpm/bin/pnpx
Installed true
Mode system_first
# vp --version
vp v1.1.0
# Linux x86_64
Used Package Manager
npm (nested project), pnpm (repo root)
Logs
### 1. Parent has pnpm-workspace.yaml (bug)
$ vpr hello
$ echo hello from ROOT ⊘ cache disabled
hello from ROOT
$ vp install --frozen-lockfile
× This project is configured to use npm
help: Run a one-off command with "pnpm dlx npm <command>", or link a npm
command that follows this project's pin with "pnpm shim add npm".
### 2. Parent pnpm-workspace.yaml removed (expected behaviour)
$ vpr hello
$ echo hello from SVC ⊘ cache disabled
hello from SVC
$ vp install --frozen-lockfile
added 1 package, and audited 2 packages in 390ms
found 0 vulnerabilities
Validations
- Read the Contributing Guidelines.
- Check that there isn't already an issue for the same bug.
- Confirm this is a Vite+ issue and not an upstream issue (Vite, Vitest, tsdown, Rolldown, or Oxc).
- The provided reproduction is a minimal reproducible example.
Written by claude-opus-5-5 via Claude Code in T3 Code on goobles-agentbox.
- Lenguaje dominante
- Rust
- Estrellas
- 6k
- Forks
- 274
- Merge medio
- 1 d 11 h
- PR fusionados (30 d)
- 206
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de voidzero-dev/vite-plus
-
pending triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
voidzero-dev/vite-plus#2882 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
voidzero-dev/vite-plus#2097 · 10 comentarios · 2 reacciones ·
Los mantenedores suelen responder en 1 día
-
`vp dev` does not print "ready in N ms"Posiblemente ocupada @fengmk2 la tomó hoy. Abiertobug
voidzero-dev/vite-plus#3053 · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
the `vp migrate` command wrongly rewrite "vite/rolldown/plugins" to "vite-plus/rolldown/plugins"Abiertopending triage
Dificultad 3/5 1-2 días Aptitud para principiantes 55/100
voidzero-dev/vite-plus#3050 ·
Los mantenedores suelen responder en 1 día
-
vp migrate crashes with "Undefined meta var" when a migrated config string contains `$`Posiblemente ocupada @BenjyLimmy la tomó hoy. Abiertobug
voidzero-dev/vite-plus#3045 · 1 asignado ·
Los mantenedores suelen responder en 1 día
Todos los issues de voidzero-dev/vite-plus
Issues similares
-
Custom hosts written as trailing-dot FQDNs (`host.local.`) aren't detected as local backendsPosiblemente ocupada @roboomp la tomó hoy. Abiertobug prio:p2 providers triaged
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
can1357/oh-my-pi#15798 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
-
requires-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
apache/datafusion-comet#7001 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
-
builtin-port enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
cmlarsen/writemorebetter#235 ·
Los mantenedores suelen responder en 1 día
-
Add a Storybook section to CONTRIBUTING.mdPosiblemente ocupada @ChanakyaG2004 la tomó hoy. Abiertodocumentation good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
FlowwStar/FlowStar#995 · 2 comentarios ·
Los mantenedores suelen responder en 1 día