Support custom .npmrc path
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 217
- Avg merge
- 8h 42m
- Merged PRs (30d)
- 1
Description
Hey, quick heads-up about the recent action update(4.2.0).
We noticed the new behavior now pulls pnpm from whatever registry is defined in a root-level .npmrc. We rely on pipeline.npmrc to point at our internal registry instead.
Could we adjust the action so that it lets us pass a custom config path? before reading the root .npmrc?
That would keep the new behavior intact without breaking setups like ours.
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 at the action's configuration-resolution entry point and inspect how the root-level .npmrc is currently read alongside the requested pipeline.npmrc path. Confirm the custom path is handled before the root configuration without removing the existing behavior, then run the action's relevant tests or CI checks to verify both registry setups.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, node.js, typescript
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100