When does pnpm create _ type links vs direct links? And how can I control it? It's breaking our mono repo setup.

[sean256]

We have a mono-repo where 5 packages depend on @someScope/[email protected]. For some reason which I cannot figure out, pnpm creates a different link to a different instance for just ONE of the 5. One of them has [email protected] in it's name.

I don't want to get into the details on why this is causing us trouble, as I don't want to spin this topic in the wrong direction. But I really want to know the logic here so I can work on syncing this up.

I will say that when I go in and manually delete and re-link the problem child, all of our issues go away.

Also, all of our packages have the same version of [email protected] listed, and so does @someScope/[email protected]

// the oddball link
../../../../node_modules/.pnpm/@[email protected][email protected]/node_modules/@someScope/react
// the normal link
../../../../node_modules/.pnpm/@[email protected]_4db1f9ae395425ec4d56821dc57dd590/node_modules/@someScope/react

If this has been answered before I apologies, I honestly couldn't figure out the right search terms for this.

[zkochan]

Looks like either @someScope/react or one of its dependencies has peer dependencies. At some place in your dependency graph, the peer dependencies are resolved, while at some other place the peer dependencies are not found. You can look into the lockfile, search for the entry of _4db1f9ae395425ec4d56821dc57dd590 and [email protected] and see how their dependencies differ.

[sean256]

If I could hug you through the internet I would. That was so helpful and with it I solved the issue.

Is there a flag or something that can be used to highlight these issues? Sort of link Lerna's host strict mode or something?

[zkochan]

Not exactly like that, but setting strict-peer-dependencies to true might help.