[BUG] GitHub org/name accesses fail about pacote HOT 7 CLOSED

To rule out a bad local configuration, I also tried on a separate Ubuntu VM and the result is the same, but git asked for credentials:

$ pacote resolve npm/cli
The authenticity of host 'github.com (140.82.118.4)' can't be established.
RSA key fingerprint is SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8.
Are you sure you want to continue connecting (yes/no)? yes
{ Error: failed '/usr/bin/git ls-remote git+ssh://[email protected]/npm/cli.git'
...

from pacote.

I'm very curious why npm can install packages from GitHub. Is it because it is using an older pacote (^9.5.9)?

from pacote.

I confirm that after reverting to 9.5.9 I can access GitHub repos using org/name, as expected.

So it must be an issue with 10.x. The next question would be why the tests did not catch it...

from pacote.

The issue is that it's preferring git+ssh over git+https for all hosted repos.

Fix coming shortly :)

from pacote.

I noticed this when my tests in npm/arborist were buzzing my phone for a 2FA authorization to use my SSH keys :)

SSH is better for private repos, since it's more straightforward for doing headless authentication with a key and doesn't require putting a basic auth in the url, but obviously not as good for public repos, which is the majority use case. Pacote 9 tries https, then falls back to ssh, which is what v10.1.6 does now as well.

from pacote.

Since I'm not familiar with the implementation details, can you confirm that the behaviour now is fully similar to that of 9.x?

I'm a bit concerned about 'Resolved url is still reported as the git+ssh url, for consistency.' Was it the same in 9.x?

from pacote.

The resolved url always being saved as ssh is new. (In v9 it was less deterministic, varying if the original url was ssh or https.) But the fetch behavior is the same as v9 now, yes.

from pacote.