JamieMason / JamieMason/syncpack
feat(update): support custom npm registries
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.1k
- Forks
- 72
- PR merge metrics
- No merged PRs in 30d
Description
## Description
In my .npmrc file I have custom npm registries for some scoped packages like
```
@foo:registry=https://gitlab.com/api/v4/projects/000000/packages/npm/
//gitlab.com/api/v4/projects/000000/packages/npm/:_authToken=000000
@bar:registry=https://gitlab.com/api/v4/projects/111111112/packages/npm/
//gitlab.com/api/v4/projects/111111112/packages/npm/:_authToken=111111112
```
## Suggested Solution
It would be nice if the update command
```
syncpack update --filter '@foo'
```
Could respect the custom registries as currently it doesn't show any available updates.
As a reference, the [NCU](https://www.npmjs.com/package/npm-check-updates) tool currently supports it, but would be nice to do this with Syncpack to avoid using one more tool. It looks like this there:
```
ncu -ws -f "@foo/*"
```
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 with the update command and its handling of .npmrc registry settings, using the scoped @foo registry and --filter '@foo' example as the reproduction. Done means syncpack update discovers available updates from the configured custom registry instead of reporting none.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100