Zoltan Kochanandgithub-actions[bot]
726d6b4a04
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
18 lines
1.2 KiB
Markdown
18 lines
1.2 KiB
Markdown
## 1100.0.11
|
|
|
|
### Major Changes
|
|
|
|
- The three registry lookups are now named for what they are keyed by, so that none of them is called `registries` — a name the `registries` setting itself has taken:
|
|
|
|
| before | after |
|
|
|---|---|
|
|
| `Config.registries` | `Config.registriesByScope` |
|
|
| `Config.namedRegistries` | `Config.registriesByPrefix` |
|
|
| `Config.registryOptions` | `Config.registryOptionsByUrl` |
|
|
|
|
The same rename applies to the `RegistryContext` fields, the `Registries` and `NamedRegistries` types (now `RegistriesByScope` and `RegistriesByPrefix`), `normalizeRegistries` / `normalizeNamedRegistries` (now `normalizeRegistriesByScope` / `normalizeRegistriesByPrefix`), and the `BUILTIN_NAMED_REGISTRIES` constant (now `BUILTIN_REGISTRIES_BY_PREFIX`).
|
|
|
|
This is an internal rename: no setting, error code, lockfile field, or `.pnpmfile.cjs` hook field changes. A `preResolution` hook still reads `ctx.registries`, which is the name pacquet passes as well. The `registries` and `namedRegistries` settings are read under the names users write them.
|
|
|
|
The pnpr resolve request sends `registriesByPrefix` where it sent `namedRegistries`. A pnpr server and its clients must be on matching versions, which is already the case for an experimental server.
|