Peter

Okay rebased this and switched over to using `onClick`, etc. but ran into some design issues I could use suggestions for. Right now this is mutating the `collapsed` property directly...

Woah! To be honest I haven't looked into profiling it at all. It sounds like maybe the old tree or flattened list isn't getting freed when the new one is...

> I switched over to testing out the latest version of your branch, and I can get the ~25M nodes to load with heap size around 3.3GB - 3.9GB Aah...

> However, collapsing/uncollapsing a node (I tested the root node) will cause an out of memory crash I'm particularly surprised that this happens at the root node, but it did...

Well that change certainly improves the root collapsing performance 😅 but the rest no so much 😬

I haven't had a chance to dig into this more recently. In the short term you're probably best off including this as a custom cell and effect you use in...

Maybe `react-laag` can detect if there's a `document.fullscreenElement` and relocate the `