[Bug?]: yarn workspaces automatically linking packages

[michaelcozzolino]

Self-service

• I'd be willing to implement a fix

Describe the bug

i have one monorepo with 2 packages ( A and B). in B I installed A using the published version on npm.
the monorepo is structured as

• root
  • package.json
  • A
    • package.json
  • B
    • package.json

i'm using yarn workspaces to manage the monorepo.
if i do yarn install in the root i see that A gets automatically linked to B, the only way to "unlink" it is to use a different version.

is this an expected behaviour? shouldn't the package be linked only if using yarn/npm link?

To reproduce

git clone https://github.com/michaelcozzolino/flyonui-vue.git

in the root run yarn install, and with ide like phpstorm you can clearly see that it is linked, or you can just edit the package.json in packages\core

Environment

System:
    OS: Linux 6.8 Ubuntu 24.04.1 LTS 24.04.1 LTS (Noble Numbat)
    CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
  Binaries:
    Node: 20.10.0 - /tmp/xfs-aad93b70/node
    Yarn: 4.6.0 - /tmp/xfs-aad93b70/yarn
    npm: 10.2.3 - ~/.nvm/versions/node/v20.10.0/bin/npm

Additional context

No response