[BUG] peerDependencies of package behave like dependencies when package is locally installed about cli HOT 1 OPEN

I either found a workaround or a solution, honestly, I can't tell. I will inline the answer here:

By default, npm install will create symlinks for file: protocol dependencies. npm install --install-links will install them as regular dependencies instead of links, solving the problem.

I have a feeling there's more going on here than I realize:

1. It feels kind of arbitrary that if my link is using a peer dependency, then I need --install-links to get the documented behavior of peerDependencies.
2. I'm developing on Windows and it does not have real symlinks. That might be playing a role here.
   1. Maybe Linux would have worked as expected in the original question.
3. Even though my answer solves the problem, the original behavior could be a bug. I've created an issue here: #7143

Regardless, this is at least one of many ways to solve the problem, so I'm posting it as an answer.

I have some additional suggestions:

1. Maybe depending on a package via file: should give a warning if that package uses peerDependencies?
2. Maybe peerDependency documentation should mention --install-links to help developers if this comes up?

from cli.