This message was deleted.

i just ran into this, if you look in your

node_modules

you likely have a nested version in there because of the npm linkl

So it is going to have to be a

peerDependency

but that unfortunately doesn’t solve the problem when it is linked. Even when using workspaces and my linked package doesn’t even have a

node_modules

directory within it (it is in the root). I’m guessing the resolution is walking up from the linked location and still finding it.