We use azure devops as a package repository and mirror which is configured via .npmrc. From taze 0.14.0 and up it fails to fetch the package versions, throwing a string of 401 errors for each package. I tried setting --loglevel debug but it doesn't provide any additional output.
Our redacted .npmrc file looks like the below:
registry=https://pkgs.dev.azure.com/#####/_packaging/#####/npm/registry/
always-auth=true
; begin auth token
### auth token here
; end auth token
I'd be happy to try and raise a PR but if I was to, aside from digging into the complexities of npm header configuration, I'd say the fix would be to revert the 0.14.0 performance fix. I think the new way you're fetching versions via raw $fetch instead of npmRegistryFetch.json might not sufficiently support the various ways npm can be configured. And not sure about anyone else but I really didn't see perf as an issue.
Lemonreds
commented
5 months ago
Describe the bug
We use azure devops as a package repository and mirror which is configured via .npmrc. From taze 0.14.0 and up it fails to fetch the package versions, throwing a string of 401 errors for each package. I tried setting --loglevel debug but it doesn't provide any additional output.
Our redacted .npmrc file looks like the below:
Command output:
I'd be happy to try and raise a PR but if I was to, aside from digging into the complexities of npm header configuration, I'd say the fix would be to revert the 0.14.0 performance fix. I think the new way you're fetching versions via raw $fetch instead of npmRegistryFetch.json might not sufficiently support the various ways npm can be configured. And not sure about anyone else but I really didn't see perf as an issue.
Reproduction
configure custom repository, run npx taze
System Info
Used Package Manager
yarn
Validations
Contributions