X-Git-Url: https://gerrit.simantics.org/r/gitweb?a=blobdiff_plain;ds=inline;f=org.simantics.maps.server%2Fnode%2Fnode-v4.8.0-win-x64%2Fnode_modules%2Fnpm%2Fhtml%2Fdoc%2Fcli%2Fnpm-link.html;fp=org.simantics.maps.server%2Fnode%2Fnode-v4.8.0-win-x64%2Fnode_modules%2Fnpm%2Fhtml%2Fdoc%2Fcli%2Fnpm-link.html;h=9572f9b65b44b981357a44c0b5fbab30980197d5;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/cli/npm-link.html b/org.simantics.maps.server/node/node-v4.8.0-win-x64/node_modules/npm/html/doc/cli/npm-link.html new file mode 100644 index 00000000..9572f9b6 --- /dev/null +++ b/org.simantics.maps.server/node/node-v4.8.0-win-x64/node_modules/npm/html/doc/cli/npm-link.html @@ -0,0 +1,78 @@ + + +
Symlink a package folder
+npm link (in package folder)
+npm link [@<scope>/]<pkgname>
+npm ln (with any of the previous argument usage)
+
Package linking is a two-step process.
+First, npm link
in a package folder will create a symlink in the global folder
+{prefix}/lib/node_modules/<package>
that links to the package where the npm
+link
command was executed. (see npm-config(7)
for the value of prefix
). It
+will also link any bins in the package to {prefix}/bin/{name}
.
Next, in some other location, npm link package-name
will create a
+symbolic link from globally-installed package-name
to node_modules/
+of the current folder.
Note that package-name
is taken from package.json
,
+not from directory name.
The package name can be optionally prefixed with a scope. See npm-scope(7)
.
+The scope must be preceded by an @-symbol and followed by a slash.
When creating tarballs for npm publish
, the linked packages are
+"snapshotted" to their current state by resolving the symbolic links.
This is handy for installing your own stuff, so that you can work on it and +test it iteratively without having to continually rebuild.
+For example:
+cd ~/projects/node-redis # go into the package directory
+npm link # creates global link
+cd ~/projects/node-bloggy # go into some other package directory.
+npm link redis # link-install the package
+
Now, any changes to ~/projects/node-redis will be reflected in +~/projects/node-bloggy/node_modules/node-redis/. Note that the link should +be to the package name, not the directory name for that package.
+You may also shortcut the two steps in one. For example, to do the +above use-case in a shorter way:
+cd ~/projects/node-bloggy # go into the dir of your main project
+npm link ../node-redis # link the dir of your dependency
+
The second line is the equivalent of doing:
+(cd ../node-redis; npm link)
+npm link node-redis
+
That is, it first creates a global link, and then links the global
+installation target into your project's node_modules
folder.
If your linked package is scoped (see npm-scope(7)
) your link command must
+include that scope, e.g.
npm link @myorg/privatepackage
+