'...
npm ERR! git clone --template=/home/uspace/.npm/_git-remotes/_templates --mirror ://github.com/debris/bignumber.js.git /home/uspace/.npm/_git-remotes/git-https-github-com-debris-bignumber-js-git-master-df3f1ce1: remote: Invalid username or password.
npm ERR! git clone --template=/home/uspace/.npm/_git-remotes/_templates --mirror //github.com/debris/bignumber.js.git /home/uspace/.npm/_git-remotes/git-https-github-com-debris-bignumber-js-git-master-df3f1ce1: fatal: Authentication failed for '//github.com/debris/bignumber.js.git/'
npm ERR! Linux 4.8.0-56-generic
npm ERR! argv "/opt/node/bin/node" "/usr/bin/npm" "install" "-g" "ethereumjs-testrpc"
npm ERR! node v6.10.3
npm ERR! npm v3.10.10
npm ERR! code 128
npm ERR! Command failed: git clone --template=/home/uspace/.npm/_git-remotes/_templates --mirror//github.com/debris/bignumber.js.git /home/uspace/.npm/_git-remotes/git-https-github-com-debris-bignumber-js-git-master-df3f1ce1
npm ERR! Cloning into bare repository '/home/uspace/.npm/_git-remotes/git-https-github-com-debris-bignumber-js-git-master-df3f1ce1'...
npm ERR! remote: Invalid username or password.
npm ERR! fatal: Authentication failed for '//github.com/debris/bignumber.js.git/'
npm ERR!
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! <//github.com/npm/npm/issues>
npm ERR! Please include the following file with any support request:
npm ERR! /home/uspace/npm-debug.log
-
Note that github.com/debris/bignumber.js doesn't exist - looks like it might have been made private...– Richard HorrocksJun 24, 2017 at 23:47
-
@RichardHorrocks There was a nasty bug affecting IOS bignumber.js (github.com/MikeMcl/bignumber.js/issues/120), web3 has a dependency on that old fork of bignumber.js and it was affected.– Ismael ♦Jun 25, 2017 at 23:49
-
1The workaround from @dylanseago github.com/ethereumjs/testrpc/issues/332 worked for me.– ponarunkumarJun 26, 2017 at 12:50
Add a comment
|
1 Answer
This is being tracked by the following tickets:
I'd suggesting following these for resolution.
answered Jun 24, 2017 at 23:49
-
Thanks for sharing the ticket details which are open. I am tracking them to find a resolution or workaround if any Jun 25, 2017 at 3:44