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.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.