Support custom npm registries for scoped packages updates

[maksnester]

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 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/*"

[rockshandy]

I came across this too, my package uses a private registry at the moment and I was hoping the general registry setting in .npmrc would let me use the private one.

[damnhandy]

In corporate environments, it highly likely that you cannot reach registry.npmjs.org directly and will be required to use an internal mirror. Sadly, syncpack doesn't seem to honor the npm config registry value and always requests packages from registry.npmjs.org.

Just looking at the code, it seems this the only place where the registry URL is hard-coded:

syncpack/src/bin-update/effects.ts

Line 143 in 8ddc298

fetchJson(`https://registry.npmjs.org/${instance.name}`),