Files
pnpm/pnpr/client/tsconfig.json
T
Zoltan Kochan c3c3e6b643 fix: resolve catalog references when installing via a pnpr server (#13233)
A `catalog:` specifier in a workspace's dependencies or overrides failed to
resolve when the install was routed through a pnpr server, erroring with
"No catalog entry '<name>' was found for catalog 'default'." even though the
catalog entry existed.

The pnpr server reconstructs the requested workspace in a temp dir from the
resolve request. That reconstruction wrote a pnpm-workspace.yaml with only a
packages: section and no catalog definitions, and passed catalogs_override:
None to the install — so the server had no catalogs and could not resolve any
catalog: specifier, in dependencies or overrides.

Forward the client's workspace catalogs in the resolve request and use them as
the install's catalogs_override, which feeds both dependency and override
catalog resolution. The client now sends its raw overrides (the server resolves
their catalog: references) instead of pre-resolving them locally.

Closes pnpm/pnpm#13232
2026-07-23 16:04:43 +02:00

26 lines
420 B
JSON

{
"extends": "@pnpm/tsconfig",
"compilerOptions": {
"outDir": "lib",
"rootDir": "src"
},
"include": [
"src/**/*.ts",
"../../__typings__/**/*.d.ts"
],
"references": [
{
"path": "../../pnpm11/catalogs/types"
},
{
"path": "../../pnpm11/core/types"
},
{
"path": "../../pnpm11/lockfile/fs"
},
{
"path": "../../pnpm11/lockfile/types"
}
]
}