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
{{ message }}
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
I am having a small bit of trouble with Private Modules. Here is the situation:
I published a private module up to NPM and it worked flawlessly. I can even install with no problem whatsoever.
When my co-workers try to install it they are getting issues about not having permission access, which I thought to be the profile that NPM is configured for on the machine (btw all windows 7 x64). This wasn't the case cause I made sure I npm login the proper information.
Then I thought it was because they had npm v1.4.28 because I found an issue as well on my computer when trying to install. I'm not really sure when this feature made it into npm but I'm sure it was version 2.x.x or higher. So I installed 2.8.9 on mine and it worked fine, but fails on the others. Its giving the same error message I would get on a 1.x.x NPM installation.
Any information would be helpful
C:\>npm -v
1.4.28
C:\>npm i @acupay-dev-team/iso-finder
npm WARN package.json @1.0.0 No description
npm WARN package.json @1.0.0 No repository field.
npm WARN package.json @1.0.0 No README data
npm WARN `git config --get remote.origin.url` returned wrong result (git://github.com/acupay-dev-tea
m/iso-finder)
npm WARN `git config --get remote.origin.url` returned wrong result (git@github.com:acupay-dev-team/
iso-finder)
npm ERR! git clone git@github.com:acupay-dev-team/iso-finder Cloning into bare repository 'C:\Users\
spugliese\AppData\Roaming\npm-cache\_git-remotes\git-github-com-acupay-dev-team-iso-finder-9f87fe94'
...
npm ERR! git clone git@github.com:acupay-dev-team/iso-finder Permission denied (publickey).
npm ERR! git clone git@github.com:acupay-dev-team/iso-finder fatal: Could not read from remote repos
itory.
npm ERR! git clone git@github.com:acupay-dev-team/iso-finder
npm ERR! git clone git@github.com:acupay-dev-team/iso-finder Please make sure you have the correct a
ccess rights
npm ERR! git clone git@github.com:acupay-dev-team/iso-finder and the repository exists.
npm ERR! addLocal Could not install acupay-dev-team/iso-finder
npm ERR! Error: ENOENT, stat 'C:\acupay-dev-team\iso-finder'
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR! <http://github.com/npm/npm/issues>
npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\n
pm\\bin\\npm-cli.js" "i" "@acupay-dev-team/iso-finder"
npm ERR! cwd C:\
npm ERR! node -v v0.10.38
npm ERR! npm -v 1.4.28
npm ERR! path C:\acupay-dev-team\iso-finder
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! C:\npm-debug.log
npm ERR! not ok code 0
C:\>npm -v
2.5.1
C:\>npm i @acupay-dev-team/iso-finder
npm WARN package.json @1.0.0 No description
npm WARN package.json @1.0.0 No repository field.
npm WARN package.json @1.0.0 No README data
@acupay-dev-team/iso-finder@1.0.5 node_modules\@acupay-dev-team\iso-finder
The text was updated successfully, but these errors were encountered:
Hello @SteveyPugs hope you've been well. We’re trying to clean up some issues. If this is still a problem, can you please reply and let us know? We’ll be happy to reopen if necessary. Thanks! -Stephanie, npm Tech Support
Gents,
I am having a small bit of trouble with Private Modules. Here is the situation:
I published a private module up to NPM and it worked flawlessly. I can even install with no problem whatsoever.
When my co-workers try to install it they are getting issues about not having permission access, which I thought to be the profile that NPM is configured for on the machine (btw all windows 7 x64). This wasn't the case cause I made sure I npm login the proper information.
Then I thought it was because they had npm v1.4.28 because I found an issue as well on my computer when trying to install. I'm not really sure when this feature made it into npm but I'm sure it was version 2.x.x or higher. So I installed 2.8.9 on mine and it worked fine, but fails on the others. Its giving the same error message I would get on a 1.x.x NPM installation.
Any information would be helpful
The text was updated successfully, but these errors were encountered: