A pnpr resolve request carries the client's registries as declarations
keyed by URL. Each declaration held one prefix, so when a project routed
two prefixes to one URL (for example through namedRegistries), only the
smallest reached the server. A dependency or lockfile entry using the
other prefix then failed on a delegated install.
The request protocol adds an `aliases` list next to `prefix`. `prefix`
stays the smallest prefix, the one lockfile keys carry, so the server keys
packages the way the client does and re-keys a lockfile entry written with
another declared prefix. `aliases` exists only in the request protocol.
pnpm-workspace.yaml refuses it in both CLIs, so no new setting is added
to v11.
The v11 config reader now defines prefix routes as own data properties,
so a `__proto__` prefix is kept instead of hitting the inherited setter.
Closespnpm/tasks#204.
---------
Co-authored-by: Zoltan Kochan <z@kochan.io>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
