npm link issue

commands.sh

[me@laptop:code/] $ cd A
[me@laptop:code/A] $ npm link                        # this works as i expect (and want)
[me@laptop:code/A] $ ll /usr/local/lib/node_modules
...
lrwxr-xr-x   1 me  admin   22 May 18 16:59 /usr/local/lib/node_modules/A -> /Users/me/code/A
...
[me@laptop:code/A] $ cd ../B
[me@laptop:code/B] $ cat package.json
...
  "dependencies": {
    "A": "0.0.x"
  }
...
[me@laptop:code/B] $ npm install --link
[me@laptop:code/B] $ ll ./node_modules                # this also works as i expect
...
lrwxr-xr-x   1 me  admin   22 May 18 16:59 node_modules/A -> /usr/local/lib/node_modules/A
...
[me@laptop:code/B] $ ll /usr/local/lib/node_modules   # global link has been replaced with static install
...
drwxr-xr-x   1 me  admin   22 May 18 16:59 /usr/local/lib/node_modules/A
...

I'm developing on both A and B, so if I blow away B, re-clone and run npm install --link, I want it to link to the global package A, and maintain that global link from the prefix to my A repository.

If I run npm link A from within B, this works, but that loses the convenience of declaring the dependencies in package.json. I could also write a script to just do this, but once again, that loses the convenience that makes npm install so great.

This looks like a bug. Please post it at https://github.com/isaacs/npm/issues

will do, thanks!

…

On May 19, 2012, at 8:20 AM, "Isaac Z. ***@***.*** wrote: This looks like a bug. Please post it at https://github.com/isaacs/npm/issues --- Reply to this email directly or view it on GitHub: https://gist.github.com/2727870