Skip to content
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

'npm install' is broken #126

Closed
darkurse opened this issue Dec 22, 2017 · 2 comments · Fixed by #127
Closed

'npm install' is broken #126

darkurse opened this issue Dec 22, 2017 · 2 comments · Fixed by #127

Comments

@darkurse
Copy link

darkurse commented Dec 22, 2017

Hi,

I cloned and tried to 'npm install' the project but it does not work.

npm verb cwd C:\Work\Others\github\angular-oauth2
npm verb Windows_NT 10.0.16299
npm verb argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\me\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "install" "--verbose"
npm verb node v6.10.3
npm verb npm  v5.6.0
npm ERR! Error while executing:
npm ERR! C:\Program Files\Git\cmd\git.EXE ls-remote -h -t ssh://[email protected]/Nikku/node-browserify.git
npm ERR!
npm ERR! Permission denied (publickey).
npm ERR! fatal: Could not read from remote repository.
npm ERR!
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.
npm ERR!
npm ERR! exited with error code: 128
npm verb exit [ 1, true ]

update

I'm not familiar with browserify so I'm gonna take two blind guesses here :

  • github.com/Nikku/node-browserify package doesnt exist and might got renamed to karma-browserify.
  • Or it seems like node-browserify was actually from repo https://github.com/substack/node-browserify/ which got itself renamed to https://github.com/browserify/browserify ( See browserify changelog for this change between version 14.4.0 and 14.5.0 )

I looked at the source on how to change this but I have honestly no clue how to fix this. Any hints ?

ps: Issue #121 mentions it but I wanted to create a proper issue entry for this

@darkurse
Copy link
Author

I think I found the reason and logged the issue on browserify repository browserify/issues/1786

@nikku
Copy link

nikku commented Jan 3, 2018

This is not related to browserify but nikku/karma-browserify#213.

I highly encourage users of karma-browserify<=4 to upgrade to the replacement karma-browserif@5:

npm i --save-dev karma-browserify@latest watchify browserify

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants