diff options
author | isaacs <i@izs.me> | 2011-09-26 22:06:37 +0400 |
---|---|---|
committer | isaacs <i@izs.me> | 2011-09-26 22:06:37 +0400 |
commit | 344649dd145ab331a5ff7a2032c100ca62dc1227 (patch) | |
tree | dba228b88dd16dcba8e91d04fbdc231e7d31590d /README.md | |
parent | c3d3b7ee8b3d006acc33f053d808b7a1f5409207 (diff) | |
parent | b3d4ca8606b7b7fdee36e25bd883f4d6db2b3b7f (diff) |
Merge remote branch 'deanlandolt/winbin' into winbin
Conflicts:
lib/utils/mkdir-p.js
lib/utils/output.js
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 31 |
1 files changed, 31 insertions, 0 deletions
@@ -62,6 +62,37 @@ However, note that github tarballs **do not contain submodules**, so those won't work. You'll have to also fetch the appropriate submodules listed in the .gitmodules file. +### Installing on Windows + +The easiest way to get up and running with npm on Windows is to clone the +[github repository](https://github.com/isaacs/npm). If you don't already have +git, [install it](https://git.wiki.kernel.org/index.php/MSysGit:InstallMSysGit) and run: + + git clone --recursive git://github.com/isaacs/npm + +If this fails with a message about "error setting certificate verify locations" +remove the failed install, set a config entry and retry, like so: + + rm -rf npm + git config --system http.sslcainfo \\bin\curl-ca-bundle.crt + git clone --recursive git://github.com/isaacs/npm + +Congratulations -- you should now have a (still very broken) npm install. Now +navigate into the newly installed npm folder: + + cd npm + +To run npm from the command line be sure to add it your PATH: + + set path="%PATH%;%CD%\bin" + +If available you can use `setx` to make this PATH addition permanent: + + setx path "%PATH%" + +Otherwise you can make this change manually in "Advanced System Settings". + + ## Permissions **tl;dr** |