We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, I get the following error when executing:
npm install loom-truffle-provider
The error:
npm ERR! code 1 npm ERR! git dep preparation failed npm ERR! command /home/user/.nvm/versions/node/v14.17.5/bin/node /home/user/.nvm/versions/node/v14.17.5/lib/node_modules/npm/bin/npm-cli.js install --force --cache=/home/user/.npm --prefer-offline=false --prefer-online=false --offline=false --no-progress --no-save --no-audit --include=dev --include=peer --include=optional --no-package-lock-only --no-dry-run npm ERR! npm WARN using --force Recommended protections disabled. npm ERR! npm ERR! code 1 npm ERR! npm ERR! The git reference could not be found npm ERR! npm ERR! command git --no-replace-objects checkout 4.0 npm ERR! npm ERR! error: pathspec '4.0' did not match any file(s) known to git
My node version is 14.17.5 and npm is 7.20.6.
14.17.5
7.20.6
It is a clean project with no other dependencies with Truffle installed globally. The only local dependency is "@truffle/hdwallet-provider": "^2.0.0"
"@truffle/hdwallet-provider": "^2.0.0"
The text was updated successfully, but these errors were encountered:
i meet it too! do you have resolved it?
#17 (comment)
i also resove it with npm i [email protected]
Sorry, something went wrong.
I got the same error too.
This fixed it for me too:
npm i [email protected]
No branches or pull requests
Hi, I get the following error when executing:
The error:
My node version is
14.17.5
and npm is7.20.6
.It is a clean project with no other dependencies with Truffle installed globally. The only local dependency is
"@truffle/hdwallet-provider": "^2.0.0"
The text was updated successfully, but these errors were encountered: