You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix from #8222 doesn't maintain scheme of replaced repo URL
Output of $ npm config get
; "user" config from /home/deck/.npmrc
prefix = "/home/deck/.local"
; node bin location = /usr/bin/node-22
; node version = v22.15.0
; npm local prefix = /home/deck/test
; npm version = 11.4.1
; cwd = /home/deck/test
; HOME = /home/deck
; Run `npm config ls -l` to show all defaults.
alexsch01
changed the title
[BUG] https://github.com/npm/cli/pull/8222 still replaces http with https
[BUG] fix from https://github.com/npm/cli/pull/8222 doesn't maintain http://
May 26, 2025
If this is intentional / npm requires https:// repositories, please close this issue
alexsch01
changed the title
[BUG] fix from https://github.com/npm/cli/pull/8222 doesn't maintain http://
[BUG] fix from https://github.com/npm/cli/pull/8222 doesn't maintain scheme of repo URL
May 26, 2025
alexsch01
changed the title
[BUG] fix from https://github.com/npm/cli/pull/8222 doesn't maintain scheme of repo URL
[BUG] fix from https://github.com/npm/cli/pull/8222 doesn't maintain scheme of replaced repo URL
May 26, 2025
; "user" config from /home/deck/.npmrc
prefix = "/home/deck/.local"
; node bin location = /usr/bin/node-22
; node version = v22.15.0
; npm local prefix = /home/deck/test
; npm version = 11.4.1
; cwd = /home/deck/test
; HOME = /home/deck
; Run `npm config ls -l` to show all defaults.
Uh oh!
There was an error while loading. Please reload this page.
Is there an existing issue for this?
This issue exists in the latest npm version
fix from #8222 doesn't maintain scheme of replaced repo URL
Output of
$ npm config get
Steps to reproduce [in Linux bash]
Current Behavior
Eventually, you'll see....
Expected Behavior
Other Information
http://localhost:8080 doesn't exist but either way the issue still happens
The text was updated successfully, but these errors were encountered: