Last pnpm version that worked
10.33.2
pnpm version
11.0.3
Code to reproduce the issue
Expected behavior
The command should output valid JSON (array, object, or NDJSON), consistent with the documented behavior of --json and with pnpm 10.x behavior.
Actual behavior
pnpm 11 prints plain text instead of JSON, for example:
@eslint/config-inspector@2.0.0
@github/copilot@1.0.39
vite@8.0.10
This is not valid JSON and cannot be parsed.
The same command in pnpm 10 returned proper JSON.
Additional information
- This regression affects tools that rely on
pnpm ls --json for global package inspection (e.g., npm‑check‑updates).
- The non‑global command
pnpm ls --json still outputs JSON correctly.
- The regression appears primarily on Windows (PowerShell), but may affect other environments.
Node.js version
24.15.0
Operating System
Windows
Last pnpm version that worked
10.33.2
pnpm version
11.0.3
Code to reproduce the issue
Expected behavior
The command should output valid JSON (array, object, or NDJSON), consistent with the documented behavior of
--jsonand with pnpm 10.x behavior.Actual behavior
pnpm 11 prints plain text instead of JSON, for example:
This is not valid JSON and cannot be parsed.
The same command in pnpm 10 returned proper JSON.
Additional information
pnpm ls --jsonfor global package inspection (e.g., npm‑check‑updates).pnpm ls --jsonstill outputs JSON correctly.Node.js version
24.15.0
Operating System
Windows