ls isn't symlink savvy #971

isaacs opened this Issue May 25, 2011 · 3 comments

3 participants

npm member
npm install connect -g

# now express will use the global connect,
# instead of installing its own.
npm install express -g

cd ~/projects/my-thing
npm link express
npm ls

# reports connect as missing, because it doesn't
# know about the global version, which is what
# connect will actually get.


Upon encountering a symbolic link, the read-installed function should traverse that directory for dependencies, rather than using the ones in the parent folder.



this would be consistent with require

npm member

These days, this:

$ npm install connect -g
$ npm install express -g

results in the express install ignoring the global connect installation and installing its own local copy.

However, on the subject of this ticket, removing the local connect and npm linking it results in npm ls showing the correct tree, with link targets included.


npm member

Yeah. It's fine how it is, I guess.

@isaacs isaacs closed this Feb 3, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment