npm install connect -g
# now express will use the global connect,
# instead of installing its own.
npm install express -g
npm link express
# 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
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.
Yeah. It's fine how it is, I guess.