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
error Command failed. Exit code: 128 Command: git Arguments: ls-remote --tags --heads ssh://git@github.com/eligrey/FileSaver.js.git Output: Host key verification failed. fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository exists.
The text was updated successfully, but these errors were encountered:
This may be related to npm/cli#4896 and GitHub removing support for the git:// protocol.
git://
If it is, my workaround while still on jsPDF v1.5.3 was to find & replace references to github: in package-lock.json:
github:
package-lock.json
"github:" => "https://github.com/"
So any reference to github:organization/repo... becomes https://github.com/organization/repo...
github:organization/repo...
https://github.com/organization/repo...
If there is any git:// in package.json / package-lock.json, you may want to also update those to instead use http://
package.json
http://
Or, you can just update your global git config with git config --global url."https://".insteadOf git://
git config --global url."https://".insteadOf git://
Sorry, something went wrong.
This issue is stale because it has been open 90 days with no activity. It will be closed soon. Please comment/reopen if this issue is still relevant.
No branches or pull requests
error Command failed.
Exit code: 128
Command: git
Arguments: ls-remote --tags --heads ssh://git@github.com/eligrey/FileSaver.js.git
Output:
Host key verification failed.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
The text was updated successfully, but these errors were encountered: