node-gradle / node-gradle/gradle-node-plugin
Support custom registry from project .npmrc in NpmSetupTask
Open
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 677
- Forks
- 120
- PR merge metrics
- No merged PRs in 30d
Description
The NpmSetupTask does not obey to the custom registry defined in .npmrc file of the project.
An ~/.npmrc does work, but it would be nice if the custom registry defined in the project specific .npmrc would als be used for NpmSetupTask.
Workaround is to use args to configure a custom registry.
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 with NpmSetupTask and inspect how it handles the project’s .npmrc versus ~/.npmrc. Reproduce the custom-registry case, compare it with the args workaround, and verify that the project-specific registry is used without requiring extra arguments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy, nodejs
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100