Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

vp treats a nested project as part of the parent's pnpm workspace, ignoring its own packageManager and lockfile

Open
  • Is something wrong?
#3,013 1 comment 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@liangmiQwQ is already working on this.

Since Oct 12, 2026.

  • #3051 by @liangmiQwQ — open

Assessment

This issue has not been assessed yet.

Description

bug enhancement
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 hello runs the root's hello script instead of svc's.
  • vp install --frozen-lockfile runs pnpm, which refuses with This project is configured to use npm. Without a packageManager field in svc/ it fails with Headless installation requires a pnpm-lock.yaml file instead.
  • vp env current inside svc/ reports pnpm 12.11.2 with source packageManager, 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

Written by claude-opus-5-5 via Claude Code in T3 Code on goobles-agentbox.

Dominant language
Rust
Stars
6k
Forks
274
Avg merge
1d 11h
Merged PRs (30d)
203

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from voidzero-dev/vite-plus

All issues in voidzero-dev/vite-plus

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.