-
-
Notifications
You must be signed in to change notification settings - Fork 614
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There is a "Repository not found" error when running "npm update" #714
Comments
Still fail to run "npm update" with node version 11, 14, 16. (nvm use 16). |
that depends on which one you want to use and on which system. for starters try version 11, otherwise higher curl -sL https://deb.nodesource.com/setup_11.x | sudo -E bash or nvm install v11.15.0 |
Still having error when runing "npm updte" using ubuntu 18 and nvm v11.15.0. ../boolberry.cc:2:10: fatal error: crypto/cryptonote_core/cryptonote_format_utils.h: No such file or directory |
I just ran "npm update" successfully after using the "github.com/jowy81/node8-multi-hashing" instead of "github.com/BlackPeter13/node8-multihashing". There are 3 high severity vulnerabilities after running the "npm update". Can I just ignore it at the moment?
|
Use node v12 |
"turtlecoin-multi-hashing": "git+https://github.com/benrod3k/node8-multi-hashing.git", |
npm ERR! Error while executing:
npm ERR! /usr/bin/git ls-remote -h -t https://github.com/turtlecoin/node8-multi-hashing.git
npm ERR!
npm ERR! ERROR: Repository not found.
npm ERR! fatal: Could not read from remote repository.
The text was updated successfully, but these errors were encountered: