You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed the scrollMonitor git url in the bower.json file was updated this morning and since then bower install is not working.
This is the error I am getting:
bower install
(node:86542) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
bower cached https://github.com/shahata/angular-viewport-watch.git#0.1.5
bower validate 0.1.5 against https://github.com/shahata/angular-viewport-watch.git#~0.1.4
bower not-cached [email protected]:stutrek/scrollMonitor.git#~1.0.12
bower resolve [email protected]:stutrek/scrollMonitor.git#~1.0.12
bower cached https://github.com/angular/bower-angular.git#1.5.9
bower validate 1.5.9 against https://github.com/angular/bower-angular.git#^1.2.0
bower ECMDERR Failed to execute "git ls-remote --tags --heads [email protected]:stutrek/scrollMonitor.git", exit code of #128 Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.
Additional error details:
Permission denied (publickey).
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:
robert-senexx
changed the title
bower install now working after scrollMonitor url update
bower install not working after scrollMonitor url update
Dec 5, 2016
Hi,
I noticed the scrollMonitor git url in the
bower.json
file was updated this morning and since thenbower install
is not working.This is the error I am getting:
I am guessing the update was done because of this issue, which now seems fixed:
bower registration was hijacked?!
Do you have any suggestions on how to fix this?
Thanks,
Robert
The text was updated successfully, but these errors were encountered: