chore(deps): bump @pnpm/napi to 12.11.2

[zkochan]

Proposed Changes

• Bumps @pnpm/napi to 12.11.2, which ships two fixes for installs with enableModulesDir: false:
  • fix(package-manager): fetch into the store when the modules dir is disabled pnpm/pnpm#16783 (12.11.1): the install fetches the registry packages the host can install into the store, while still writing no node_modules, as pnpm v10 did.
  • fix(package-manager): fetch the packages reused from the lockfile when the modules dir is disabled pnpm/pnpm#16797 (12.11.2): it also fetches the packages it reuses from an existing lockfile, not only the ones it resolves.
• fusepm installs this way and serves node_modules from the store. When packages are missing from the store, the FUSE daemon downloads each one the first time it is read. In the ripple container, compiling a component whose capsule has about 5,500 dependencies took 3 minutes with 12.11.0 instead of 8 seconds. With a lockfile restored from the dependency graph (fix(pnpm): restore the lockfile settings a dependency graph was resolved under #10784), 12.11.1 still left about a third of the packages unfetched.
• The lockfile also gains command-bar's chai dependency, which refactor: decouple component ui from preview, compositions and command-bar #10771 added without updating the lockfile. Any bit install on master produces this change.

🤖 Generated with Claude Code

[qodo-free-for-open-source-projects]

PR Summary by Qodo

Bump @pnpm/napi to 12.11.1 to restore store prefetching

🐞 Bug fix ⚙️ Configuration changes 🕐 10-20 Minutes

AI Description

• Pin @pnpm/napi 12.11.1 to restore package fetching during installs without node_modules.
• Refresh lockfile entries and platform binaries so fusepm can mount packages from the populated
 store.

Diagram

graph TD
  A["Version pin"] --> B["pnpm install"] --> C[("Package store")] --> D["FUSE mount"] --> E["Component build"]

Loading

High-Level Assessment

Taking the targeted upstream fix and updating its lockfile resolutions is preferable to changing fusepm's install flow or relying on first-access downloads. The diff includes no application-code changes or tests.

Files changed (2) +77 / -77

Other (2) +77 / -77

workspace.jsoncPin @pnpm/napi to 12.11.1 +1/-1

Pin @pnpm/napi to 12.11.1

• Updates the workspace dependency from 12.11.0 to 12.11.1 to pick up the fix for store fetching when enableModulesDir is false.

workspace.jsonc

pnpm-lock.yamlResolve pnpm binding and native binaries at 12.11.1 +76/-76

Resolve pnpm binding and native binaries at 12.11.1

• Updates importer and snapshot references, package integrity hashes, and optional platform-specific @pnpm/napi binaries to match the new pin. No unrelated dependency changes appear in the patch.

pnpm-lock.yaml

[qodo-free-for-open-source-projects]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0) 🎨 UX issues (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

1. Command-bar tests fail under Chai 5 ⊘ Outdated

Description

The command-bar test statically imports Chai, but the resolved workspace peer is now chai@5.2.1
while the repository’s Mocha/Babel setup transforms test modules to CommonJS. Running the component
test therefore attempts to load Chai 5 with require() and fails before the assertions execute.

Code

pnpm-lock.yaml[58924]

+      chai: 5.2.1

Evidence

The changed lockfile adds a command-bar importer dependency on chai@5.2.1 and a matching
peer-resolved snapshot. The command-bar test uses a static Chai import, while the repository’s test
bootstrap and Babel configuration explicitly transform TypeScript test modules to CommonJS; the
workspace policy otherwise pins Chai to 4.3.0.

pnpm-lock.yaml[19014-19016]
pnpm-lock.yaml[58909-58924]
scopes/explorer/command-bar/command-bar.ui.runtime.spec.tsx[1-1]
babel-register.js[1-9]
babel.e2e.config.js[13-28]
workspace.jsonc[449-453]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The lockfile resolves the command-bar component’s Chai peer to `5.2.1`, but its test is transformed to CommonJS and statically imports Chai, so the test runner cannot load the ESM-only Chai 5 package.
## Fix Focus Areas
- pnpm-lock.yaml[19014-19016]
- pnpm-lock.yaml[58909-58924]
- scopes/explorer/command-bar/command-bar.ui.runtime.spec.tsx[1-1]
- babel.e2e.config.js[13-28]
## Recommended Fix
Regenerate the lockfile so the command-bar importer and its snapshots resolve `chai@4.3.0`, matching the workspace policy and the CommonJS test runner. If Chai 5 is required, instead migrate this test path to an ESM-compatible runner and verify all affected component tests.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

Tip of the day

💡 Did you know, you can copy the agent prompt from any finding and feed it to your IDE agent

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[qodo-free-for-open-source-projects]

Code review by qodo was updated up to the latest commit b14dacd

[qodo-free-for-open-source-projects]

Code review by qodo was updated up to the latest commit 55108a2

[qodo-free-for-open-source-projects]

Code review by qodo was updated up to the latest commit 04b29a3