v0.4.9

Adds pnpm named-registry support, so dependencies that resolve through a registry alias install under nub.

Named registries

When pnpm is the incumbent package manager, nub now honors pnpm's namedRegistries — an alias-to-registry-URL map declared in pnpm-workspace.yaml or the global pnpm config.yaml. A dependency spec prefixed with the alias resolves from that registry:

# pnpm-workspace.yaml
namedRegistries:
  work: https://npm.example.com/

// package.json
{ "dependencies": { "@work/constants": "work:1.x.x" } }

Both direct and transitive named-registry specs resolve. The built-in gh: alias points at GitHub Packages (https://npm.pkg.github.com/), and a user entry can repoint it at a GitHub Enterprise host. Authentication is read from existing per-URL .npmrc entries — //host/:_authToken=… — so no new auth configuration is needed. (#444, #440)

Before this, a named-registry spec fell through to the default registry and failed to resolve (no version of @work/constants matches range work:1.x.x).

---

What's Changed

• feat(resolver): support pnpm namedRegistries in pnpm-compat mode by @colinhacks in #444

Full Changelog: v0.4.8...v0.4.9