Kristoffer K.

#4036 shouldn't affect the `node-modules` linker since it doesn't use it.

Closing due to no response and no reproduction provided.

Running Sherlock again to check

Were you able to figure out what was going on? > I've tried to create a minimal repro and so far haven't been successful That's fine, as long as you...

This should have been fixed by https://github.com/yarnpkg/berry/pull/4928 which was released in v3.2.4 so I'll close this, if you're still able to reproduce we can reopen.

You can use env variables to set the node linker, if you define `YARN_NODE_LINKER="node-modules"` Yarn will use that instead of whatever is in your config. Ref note at the top...

> The lookup is simply require.resolve(), so I'm curious if Y2 has limitations around that Not a limitation, it's running `require.resolve(foo)` which means it will try to resolve `@beemo/driver-typescript` from...

Depends on the use case, Babel does it to load plugins and presets relative to the config that declared it https://github.com/babel/babel/blob/a647b9ea6bdd510f0d80b58dbea66828016ffe00/packages/babel-core/src/config/files/plugins.ts#L93-L148 The docs explains it in more details https://yarnpkg.com/advanced/rulebook#packages-should-only-ever-require-what-they-formally-list-in-their-dependencies

This isn't Yarn 2 specific so there is no need to label it as such, it's an issue that should be fixed for all package managers, though Yarn in PnP...

> rollup-plugin-pnp-resolve wasn't added but is mentioned in #688 (comment) and #458 (comment) `resolve`, which is used by `@rollup/plugin-node-resolve`, has PnP support so that rollup plugin isn't needed anymore.