microsoft / microsoft/nodejstools
Support scoped registries in .npmrc
Open
Nobody has claimed this yet.
feature
npm-integration
- Dominant language
- C#
- Stars
- 1.8k
- Forks
- 355
- PR merge metrics
- No merged PRs in 30d
Description
The NTVS package dialog does a good job of supporting a custom registry in .npmrc:
registry = 'http://npm.mycompany.com/'
However, it is often preferable to use a scope for private NPM packages and leave the public registry unchanged:
@mycompany:registry = 'http://npm.mycompany.com/'
This significantly reduces the burden on a private NPM registry, since it only has to serve requests for scoped packages.
Contributor guide
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 in the NTVS package dialog code and trace how it reads custom registry settings from .npmrc. Support scoped entries such as @mycompany:registry while preserving the existing unscoped registry behavior, and verify the dialog handles both forms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, node.js
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100