When you reported this, you were using a then-current version of npm, but there have been a lot of improvements to npm since 1.4.14. If this is not working on Windows, then it should be classified as a bug. npm works this way by default on Unix-like machines, where the bin scripts specified by package.json are installed to /usr/local/bin or similar. In any case, it sounds like you are trying to configure npm such that a globally installed module is available to all users on a specific machine.
this directory is only visible to me, and not shared with other users. Npm ERR! C:\Users\tenten0213\Documents\develop\npm-debug.I think that part of the issue here is that global means "across all modules" and stands opposed to "for this module only".įor example, when I use npm I am using nvm to switch between versions of node and npm, and npm install -global actually winds up installing somewhere under ~/.nvm/versions. Npm ERR! Additional logging details can be found in: Npm ERR! cwd C:\Users\tenten0213\Documents\develop Npm ERR! network 'proxy' config is set properly. Npm ERR! network If you are behind a proxy, please make sure that the Npm ERR! network In most cases you are behind a proxy or have bad network settings.
Npm ERR! network and is related to network connectivity. Npm ERR! network This is most likely not a problem with npm itself Npm ERR! network tunneling socket could not be established, cause=7252:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:openssl\ssl\s23_clnt.c:766:
0 kommentar(er)
