X-Git-Url: https://gerrit.simantics.org/r/gitweb?a=blobdiff_plain;f=org.simantics.maps.server%2Fnode%2Fnode-v4.8.0-win-x64%2Fnode_modules%2Fnpm%2Fhtml%2Fdoc%2FREADME.html;fp=org.simantics.maps.server%2Fnode%2Fnode-v4.8.0-win-x64%2Fnode_modules%2Fnpm%2Fhtml%2Fdoc%2FREADME.html;h=9c66c0eea90ae2c6b373e57b8966c236fd62586f;hb=2529be6d456deeb07c128603ce4971f1dc29b695;hp=0000000000000000000000000000000000000000;hpb=2636fc31c16c23711cf2b06a4ae8537bba9c1d35;p=simantics%2Fdistrict.git diff --git a/org.simantics.maps.server/node/node-v4.8.0-win-x64/node_modules/npm/html/doc/README.html b/org.simantics.maps.server/node/node-v4.8.0-win-x64/node_modules/npm/html/doc/README.html new file mode 100644 index 00000000..9c66c0ee --- /dev/null +++ b/org.simantics.maps.server/node/node-v4.8.0-win-x64/node_modules/npm/html/doc/README.html @@ -0,0 +1,131 @@ + + +
a JavaScript package manager
+ +This is just enough info to get you up and running.
+Much more info available via npm help
once it's installed.
You need node v0.10 or higher to run this program.
+To install an old and unsupported version of npm that works on node 0.3 +and prior, clone the git repo and dig through the old tags and branches.
+npm is configured to use npm, Inc.'s public package registry at +https://registry.npmjs.org by default.
+You can configure npm to use any compatible registry you +like, and even run your own registry. Check out the doc on +registries.
+Use of someone else's registry may be governed by terms of use. The +terms of use for the default public registry are available at +https://www.npmjs.com.
+npm is bundled with node.
+Get the MSI. npm is in it.
+Get the pkg. npm is in it.
+Run make install
. npm will be installed with node.
If you want a more fancy pants install (a different version, customized +paths, etc.) then read on.
+There's a pretty robust install script at +https://www.npmjs.com/install.sh. You can download that and run it.
+Here's an example using curl:
+curl -L https://www.npmjs.com/install.sh | sh
+
+You can set any npm configuration params with that script:
+npm_config_prefix=/some/path sh install.sh
+
+Or, you can run it in uber-debuggery mode:
+npm_debug=1 sh install.sh
+
+Get the code with git. Use make
to build the docs and do other stuff.
+If you plan on hacking on npm, make link
is your friend.
If you've got the npm source code, you can also semi-permanently set
+arbitrary config keys using the ./configure --key=val ...
, and then
+run npm commands by doing node cli.js <cmd> <args>
. (This is helpful
+for testing, or running stuff without actually installing npm itself.)
You can download a zip file from https://github.com/npm/npm/releases, and
+unpack it in the node_modules\npm\
folder inside node's installation folder.
To upgrade to npm 2, follow the Windows upgrade instructions in +the npm Troubleshooting Guide:
+https://github.com/npm/npm/wiki/Troubleshooting#upgrading-on-windows
+If that's not fancy enough for you, then you can fetch the code with +git, and mess with it directly.
+No.
+So sad to see you go.
+sudo npm uninstall npm -g
+
+Or, if that fails,
+sudo make uninstall
+
+Usually, the above instructions are sufficient. That will remove +npm, but leave behind anything you've installed.
+If you would like to remove all the packages that you have installed,
+then you can use the npm ls
command to find them, and then npm rm
to
+remove them.
To remove cruft left behind by npm 0.x, you can use the included
+clean-old.sh
script file. You can run it conveniently like this:
npm explore npm -g -- sh scripts/clean-old.sh
+
+npm uses two configuration files, one for per-user configs, and another +for global (every-user) configs. You can view them by doing:
+npm config get userconfig # defaults to ~/.npmrc
+npm config get globalconfig # defaults to /usr/local/etc/npmrc
+
+Uninstalling npm does not remove configuration files by default. You +must remove them yourself manually if you want them gone. Note that +this means that future npm installs will not remember the settings that +you have chosen.
+Check out the docs, +especially the faq.
+You can use the npm help
command to read any of them.
If you're a developer, and you want to use npm to publish your program, +you should read this
+When you find issues, please report them:
+Be sure to include all of the output from the npm command that didn't work
+as expected. The npm-debug.log
file is also helpful to provide.
You can also look for isaacs in #node.js on irc://irc.freenode.net. He +will no doubt tell you to put the output in a gist or email.
+