I'm opening this issue because:

• npm is crashing.
• npm is producing an incorrect install.
• npm is doing something I don't understand.
• Other (see below for feature requests):

What's going wrong?

• Given a NPM package 'a'
• Given the package 'a' npm linked
• Given another NPM package 'b'
• Given package 'a' is npm link a in package 'b'
• Given package c is installed npm install c
• I would expect to have both 'a' and 'c' packages inside b's node_modules/
• What happens is that package 'a' get's unlinked from 'b'

How can the CLI team reproduce the problem?

I think description above should be enough

supporting information:

• npm -v prints:
  5.0.2
• node -v prints:
  6.10.3
• npm config get registry prints:
  https://registry.npmjs.org/
• Windows, OS X/macOS, or Linux?:
  Windows 8.1 64-bit, git-bash as a shell