npm Community Forum (Archive)

The npm community forum has been discontinued.

To discuss usage of npm, visit the GitHub Support Community.

npm ls reports UNMET DEPENDENCY, missing for linked packages

After linking with npm link, the dependency is reported as UNMET DEPENDENCY.

Preparation:
cd /tmp
git clone git@github.com:alexgorbatchev/node-crc.git
cd node-crc
npm link
cd …
mkdir foo
cd foo
npm init
npm install --save crc

Then npm ls reports:

foo@1.0.0 /tmp/foo
└─┬ crc@3.8.0
  └─┬ buffer@5.2.1
    ├── base64-js@1.3.0
    └── ieee754@1.1.12

Then do npm link crc and afterwards npm ls reports

foo@1.0.0 /tmp/foo
└─┬ UNMET DEPENDENCY crc@3.8.0
  └─┬ buffer@5.2.1
    ├── base64-js@1.3.0
    └── ieee754@1.1.12
npm ERR! missing: crc@3.8.0, required by foo@1.0.0

Any explanations / documentation on this?

Tested with npm@latest, which is version 6.5.0 ATM.