[Query] What is the best way to debug Link Step Issues?

[manoraj]

Version: 3.6.1

I am migrating our monorepo project from Yarn v1 to Yarn Berry v3 and facing issues with the Link step getting stuck during yarn install and throwing an error at the end.

`<--- Last few GCs --->

[95334:0x130078000] 1979302 ms: Mark-sweep 4053.9 (4131.6) -> 4051.7 (4131.3) MB, 613.4 / 0.0 ms (average mu = 0.589, current mu = 0.143) allocation failure; scavenge might not succeed
[95334:0x130078000] 1980682 ms: Mark-sweep 4067.7 (4131.3) -> 4065.5 (4160.8) MB, 1359.9 / 0.0 ms (average mu = 0.284, current mu = 0.014) allocation failure; scavenge might not succeed

<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
1: 0x1005966e4 node::Abort() [/Users/mk/.nvm/versions/node/v18.17.0/bin/node]`

Question: How can I debug the issues with yarn install in general? In this case, I want to understand why the Link step is failing.

[manoraj]

Turns out that the build step is causing this issue. I can confirm that yarn install --mode=skip-build is passing without errors. But, how can I proceed from here?

Need help in debugging suggestions further to understand possible issues and find the root cause.