That is definitely incorrect. It looks like hosted-git-info may be returning bogus SSH URLs in some cases. I'll take a look. Thanks!

wow,
git+null:[email protected]:qubitdigital/ambassador.git#a37f7f62fb1636cb0fe08fc65a233218a0fab334
is extra invalid.

It looks like 'git+' + protocol + ':' + info.ssh() and not 'info.sshurl()'

An actual valid URL would look like:

git+ssh://[email protected]/qubitdigital/ambassador.git#a37f7f62fb1636cb0fe08fc65a233218a0fab334

Ah, yup:

https://github.com/npm/npm/blob/master/lib/cache/add-remote-git.js#L87

Should be sshurl()

Which is then further mangled by:

https://github.com/npm/npm/blob/master/lib/cache/add-remote-git.js#L415-L419

To result in the confusing bit above.

Thanks for tracking that down, @iarna. For cloning purposes, npm needs .ssh(), but for saving purposes, is needs .sshurl() – it may be necessary to pass the parsed hostInfo all the way through, at least as far as getResolved. I'll investigate.

Fixed in 387f889. Thanks for bringing this up! This will be part of the next patch release, going out very soon (like, less than an hour).

...and indeed, this was included as part of [email protected].

For the record, just using sshurl proved to be insufficient, as sshurl now returns a git+ssh protocol and git only actually supports the ssh protocol and scp-style non-urls.