Support registry-url, scope and NODE_AUTH_TOKEN
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 140
- Forks
- 19
- Avg merge
- 13h 19m
- Merged PRs (30d)
- 3
Description
We have private company packages hosted on github packages. With setup-node we'd use the registry-url, scope and NODE_AUTH_TOKEN to set the auth when installing and publishing packages. Would be nice if pnpm/setup could support this.
Right now I have a workaround but it requires indirect setup and env vars (ci.npmrc for ci only and NPM_CONFIG_USERCONFIG pointing to it)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining how pnpm/setup currently configures package installation and publishing, then compare the requested behavior with setup-node's registry-url, scope, and NODE_AUTH_TOKEN inputs. Verify the result against private packages hosted on GitHub Packages, with installation and publishing working without ci.npmrc or NPM_CONFIG_USERCONFIG workarounds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, node.js
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100