Aquesta és una versió anterior. La versió actual és la 0.9.7. Nub 0.9.7 · Data de publicació:
Fitxers d’instal·lació 0.4.9
| Arquitectura | Tipus | Àmbit | Mida del fitxer | Baixa | SHA256 |
|---|---|---|---|---|---|
| 64 bits | ZIP → Portable | — | — | github.com | VirusTotal |
| ARM64 | ZIP → Portable | — | — | github.com | VirusTotal |
L’enllaç i l’SHA256 provenen del manifest comunitari del Gestor de paquets del Windows. Convé comparar el hash del fitxer baixat abans d’executar-lo.
Notes de la versió
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
