table of contents
other versions
- jessie 1.4.21+ds-2
- testing 5.8.0+ds6-3
- stretch-backports 5.8.0+ds6-2~bpo9+1
- unstable 5.8.0+ds6-4
other sections
NPM-LINK(1) | NPM-LINK(1) |
NAME¶
npm-link - Symlink a package folderSYNOPSIS¶
npm link (in package folder) npm link <pkgname> npm ln (with any of the previous argument usage)
DESCRIPTION¶
Package linking is a two-step process. First, npm link in a package folder will create a globally-installed symbolic link from prefix/package-name to the current folder. Next, in some other location, npm link package-name will create a symlink from the local node_modules folder to the global symlink. Note that package-name is taken from package.json, not from directory name. 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
-
cd ~/projects/node-bloggy # go into the dir of your main project npm link ../node-redis # link the dir of your dependency
-
(cd ../node-redis; npm link) npm link redis
SEE ALSO¶
- •
- npm help developers
- •
- npm help faq
- •
- npm help package.json
- •
- npm help install
- •
- npm help folders
- •
- npm help config
- •
- npm help config
- •
- npm help npmrc
August 2014 |