mirror of https://github.com/pnpm/pnpm.git synced 2026-06-28 09:55:39 -04:00

Files

Zoltan Kochan 681b593eb2 fix: support scope-specific registry auth tokens (#12392 )

pnpm can now use different auth tokens for different package scopes, even when those scopes use the same registry URL.

Previously, auth was selected only by registry URL. If `@org-a` and `@org-b` both used `https://npm.pkg.github.com/`, they had to share the same token. This caused problems for registries that issue tokens per organization or per scope.

Configure a scope-specific token by adding the package scope after the registry URL in the auth key:

```ini
@org-a:registry=https://npm.pkg.github.com/
@org-b:registry=https://npm.pkg.github.com/

//npm.pkg.github.com/:@org-a:_authToken=${ORG_A_TOKEN}
//npm.pkg.github.com/:@org-b:_authToken=${ORG_B_TOKEN}

//npm.pkg.github.com/:_authToken=${FALLBACK_TOKEN}
```

`pnpm login --registry=https://npm.pkg.github.com --scope=@org-a` writes the token to the same scope-specific auth key.

When installing or publishing `@org-a/*`, pnpm uses `ORG_A_TOKEN`. For `@org-b/*`, pnpm uses `ORG_B_TOKEN`. Packages without a matching scope continue to use the registry-wide fallback token.

2026-06-14 11:43:30 +02:00

src

fix: support scope-specific registry auth tokens (#12392 )

2026-06-14 11:43:30 +02:00

test

fix: support scope-specific registry auth tokens (#12392 )

2026-06-14 11:43:30 +02:00

CHANGELOG.md

chore(release): 11.6.0 (#12336 )

2026-06-12 00:53:15 +02:00

example.js

refactor: rename internal packages to @pnpm/<domain>.<leaf> convention (#10997 )

2026-03-17 21:50:40 +01:00

package.json

chore(release): 11.6.0 (#12336 )

2026-06-12 00:53:15 +02:00

README.md

docs: fix package names in README files (#11409 )

2026-04-30 22:59:17 +02:00

tsconfig.json

perf: replace node-fetch with undici (#10537 )

2026-03-29 12:44:00 +02:00

tsconfig.lint.json

refactor: put all non-public projects to directories that start with __

2022-11-20 02:40:44 +02:00

README.md

@pnpm/resolving.npm-resolver

Resolver for npm-hosted packages

Installation

pnpm add @pnpm/resolving.npm-resolver

Usage

'use strict'
const createResolveFromNpm = require('@pnpm/resolving.npm-resolver').default

const resolveFromNpm = createResolveFromNpm({
  store: '.store',
  offline: false,
  rawConfig: {
    registry: 'https://registry.npmjs.org/',
  },
})

resolveFromNpm({alias: 'is-positive', bareSpecifier: '1.0.0'}, {
  registry: 'https://registry.npmjs.org/',
})
.then(resolveResult => console.log(JSON.stringify(resolveResult, null, 2)))
//> {
//    "id": "registry.npmjs.org/is-positive/1.0.0",
//    "latest": "3.1.0",
//    "package": {
//      "name": "is-positive",
//      "version": "1.0.0",
//      "devDependencies": {
//        "ava": "^0.0.4"
//      },
//      "_hasShrinkwrap": false,
//      "directories": {},
//      "dist": {
//        "shasum": "88009856b64a2f1eb7d8bb0179418424ae0452cb",
//        "tarball": "https://registry.npmjs.org/is-positive/-/is-positive-1.0.0.tgz"
//      },
//      "engines": {
//        "node": ">=0.10.0"
//      }
//    },
//    "resolution": {
//      "integrity": "sha1-iACYVrZKLx632LsBeUGEJK4EUss=",
//      "registry": "https://registry.npmjs.org/",
//      "tarball": "https://registry.npmjs.org/is-positive/-/is-positive-1.0.0.tgz"
//    },
//    "resolvedVia": "npm-registry"
//  }

License

MIT