[BUG] ENOENT: no such file or directory, open

[maksimr]

node --version  
v14.15.3
npm --version  
6.14.9

STR:

mkdir -p /tmp/p/zoo && cd  /tmp/p/zoo && npm init -y \
&& mkdir -p /tmp/p/bar && cd  /tmp/p/bar && npm init -y && npm install ../zoo \
&& mkdir -p /tmp/p/foo && cd  /tmp/p/foo && npm init -y && npm install ../zoo ../bar

 cd  /tmp/p/foo && npm ci

npm WARN prepare removing existing node_modules/ before installation
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /private/tmp/p/foo/node_modules/bar/node_modules/zoo/package.json
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open '/private/tmp/p/foo/node_modules/bar/node_modules/zoo/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

Maybe relates to #529

[maksimr]

The problem with local packages. When you try to install local package bar which has as a dependency another local package zoo inside package foo you would get an error. If open node_modules you can see that npm ci create broken symlink /private/zoo but should be /private/tmp/p/zoo

[darcyclarke]

npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.

If your bug is preproducible on v7, please re-file this issue using our new issue template.

If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo