Zoltan Kochan
760b2ece2c
Close the four CLI-surface differences left over from pnpm/pnpm#13315 after pnpm/pnpm#13359 and pnpm/pnpm#13375 landed the other two. Three land in the Rust engine. The `Scope:` line arrives via a new `pnpm:scope` channel and a port of `reportScope.ts`; pnpm gates it on the command being one that reports scope *and* the run being workspace-wide, and since the engine's recursive-by-default set is narrower than pnpm's, that conjunction is computed at dispatch and seeded into the reporter. The event is emitted where the counts already exist — the `--filter` resolution and the installer's workspace walk — so no install pays for a second directory walk. A `sharedWorkspaceLockfile: false` plan reports once for the whole selection rather than once per child install, which would otherwise overwrite the filtered count with the workspace total. The second is the `allowBuilds` placeholder an install writes for a build it blocked, which pnpm/pnpm#13375 taught the engine to read but not yet to write. The third is the elapsed time on a cache-satisfied lockfile verdict. The fourth goes the other way. The store block a first install prints is unreachable in the TypeScript CLI: `reportContext` needs `pnpm:package-import-method`, which only `@pnpm/fs.indexed-pkg-importer` emits, and that runs inside a `@pnpm/worker` thread whose logger never reaches the reporter. The main process already receives the import method back from the worker, so it is reported from there instead. Reporter globals are now seeded before the pre-command checks. They are `OnceLock`s and the pre-command checks emit, so whatever fired first was locking in unset values. Closes pnpm/pnpm#13315
380 B
380 B
pacquet
| pacquet |
|---|
| patch |
pnpm install, run, test, update, remove, link, unlink, prune, and rebuild now print the workspace scope they resolved — Scope: all 41 workspace projects, or Scope: 5 of 41 workspace projects under a --filter. This is the confirmation that a filter selected what was intended #13315.