[Bug?]: yarn link failing with NodeModulesLinker: "Assertion failed: Writing attempt prevented to ..."

[itsjamie]

Self-service

• I'd be willing to implement a fix

Describe the bug

Two projects, that are both setup as yarn workspaces separately. Looking to run yarn link -r ../sibling-project/javascript.

Fails with:

Assertion failed: Writing attempt prevented to <snip>/sibling-project/javascript/node_modules/lodash-es which is outside project root: <snip>/main-project

To reproduce

sibling-project package.json has a workspaces field that indicates javascript is a workspace.
main-project contains many package-based workspaces, and is trying to link a non-migrated dependency in as a dependency.

Environment

System:
OS: macOS 11.5.2
CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
Binaries:
Node: 12.20.1 - /private/var/folders/rz/8pj9lzz12fqfx51ddh4x5k813x2t56/T/xfs-c9714123/node
Yarn: 3.0.1 - /private/var/folders/rz/8pj9lzz12fqfx51ddh4x5k813x2t56/T/xfs-c9714123/yarn
npm: 6.14.10 - ~/.nvm/versions/node/v12.20.1/bin/npm

Additional context

No response

[larixer]

Fixed in #3183, merged, but not released yet. To try the fix use yarn set version from sources and then yarn to install dependencies using version with the fix.

[merceyz]

It's in the canary release at the moment so you can alternatively run

yarn set version canary && yarn

[kldavis4]

This still seems like an issue for me with 3.2.0-rc.7 using the node-modules nodeLinker. Any ideas what might be going on?

[larixer]

@kldavis4 Please open a new issue with reproduction. If you want to troubleshoot a bit yourself, you can use NM_DEBUG_LEVEL=2 yarn to see the hoisted tree and check with the write path in the error message.