Question: Using no-cycle causes a node to run out of heap memory

[Nokel81]

I am attempting to turn on your no-cycle rule on a repo, namely with lensapp/lens#3547. However, I have run into node (v14) running out of heap memory. I was wondering if you had any pointers as to why this might be happening.

I have tried reducing the depth to 5. With that it no longer runs out of heap memory but instead takes over half an hour to lint (previously it would take about 2 minutes).

[ljharb]

To work, the rule has to build up a model of your entire dependency graph. I would expect, however, that there's a lot of improvement to be had here. (Related: #1944 #1943 #2076 #788)