Tried using this multiple times but you end up having to override so much it's barely worth using. Doesn't really solve any of the real problems you have regarding dialogs e.g. capturing/locking focus, displaying on top no matter the parent styles, etc. It's basically ~30 lines of CSS you could/should have written yourself.
This article does not show a single performance measurement. Does any of this *actually* improve performance? You can't optimise if you don't measure. You're not optimising if you're not measuring.
Note the node event loop is not dissimilar to the event loop in the browser. There's a great talk explaining
the browser event loop, tasks, microtasks, etc and how they're scheduled with CSS, Animations the DOM in this talk from Jake Archibald at 2018 JSConf Asia: https://www.youtube.com/watch?v=cCOL7MC4Pl0