Userconfig = "C:\\Users\\yangb-g\\.npmrc" Tmp = "C:\\Users\\yangb-g\\AppData\\Local\\Temp" Init-module = "C:\\Users\\yangb-g\\.npm-init.js" Globalconfig = "C:\\Users\\yangb-g\\AppData\\Roaming Prefix = "C:\\Users\\yangb-g\\AppData\\RoamingĬache = "C:\\Users\\yangb-g\\AppData\\Roaming NPM configuration is as follows λ npm config ls -l The environmental background of the problem and what methods have you tried We are trying to clean up older npm issues, so if we don't hear back from you within a week, we will close this issue.The NPM installation package always times out, and there is no agent for NPM configuration Can you try updating your npm installation and let us know if the problem is still present in update npm on Windows, follow the instructions here: 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. 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.
0 kommentar(er)
