@davetayls Does this happen on [email protected] as well?

I have a similar issue, which i can replicate on 2.7.6 as well. Note that I'm using the shrinkwrap feature, where it even though the url is directly specified in the package.json using git+https, it has recorded it as git+ssh in the shrinkwrap.

Hey. Sorry for the late reply, it went mental yesterday. I'm using the shrink wrap feature as well. I'll try the build with 2.7.6 this morning and feed back.

Seeing this on heroku as well. Forced it to use the 2.7.6 version and it still fails.

Rolled back npm to version 2.7.3 and it works fine, so I guess it's a problem introduced in 2.7.4

I'm finding it quite tricky to test this without causing an issue to the testers, i think it works locally because i have the correct ssh keys for the ssh url to work. seems @kanongil and @cgreening can replicate as well which is useful 👍 thanks

+1 Still a problem with [email protected]

This should be fixed in [email protected] (current npm@next). Could you verify that it works for you?

Better, but it seems be missing the credentials that should be passed in the https url

 Npm version changed (2.7.3 => 2.8.0); invalidating cache
       Installing node modules
       npm ERR! git clone --template=/app/.npm/_git-remotes/_templates --mirror https://bitbucket.org/cgreening/noduleio.git /app/.npm/_git-remotes/https-bitbucket-org-cgreening-noduleio-git-5d0f1af7: Cloning into bare repository '/app/.npm/_git-remotes/https-bitbucket-org-cgreening-noduleio-git-5d0f1af7'...
       npm ERR! git clone --template=/app/.npm/_git-remotes/_templates --mirror https://bitbucket.org/cgreening/noduleio.git /app/.npm/_git-remotes/https-bitbucket-org-cgreening-noduleio-git-5d0f1af7: fatal: Authentication failed for 'https://bitbucket.org/cgreening/noduleio.git/'

In my package json the dependencies look like:

"noduleio": "git+https://cgreening:[email protected]/cgreening/noduleio.git"

This is one of the paths that I apparently didn't test enough – I can replicate that the credentials are getting stripped from the URLs and am working on a fix.

The fix for @cgreening's issue landed in 15efe12, and after banging on it some more, I'm confident that this is something that [email protected] (out very shortly) addresses.

Thanks very much :)

Works on 2.8.1

Thanks!

I'm still seeing this. What is the preferred way of downgrading npm to a specific version?

@iMerica What version are you still seeing this on? If you want to downgrade to, say, 2.7.3 for whatever reason:

$ npm install -g [email protected]