The goal is have custom nodes and custom layout algorithm working together without new non-measured nodes displaying before position is set (aka "flickering"). I have seen the topic being discussed before and people are confused, including me :-)

I would expect this to include measurements on hidden nodes:

useNodesInitialized({
    includeHiddenNodes: true,
  });

But no... this is what I think is happening based on reading docs and testing behaviour etc:

Hidden nodes are equivalent to remove something from the DOM in HTML, not just "hiding". If this is the case then I understand why you can't measure "removed" elements in the DOM, but the hidden/visible is ambiguous imo.

Also it explains why nodes won't be initialized if they are "removed" - and why useNodesInitialized will never return true if you include nodes that never can be initialized. But then I don't understand the point of the includeHiddenNodes option - i.e. why it is useful.

I might of course have totally misunderstood, but if not, then what I wish is:

1. Clearer, more explicit naming (e.g. removed instead of hidden)
2. A clean solution for the measure first problem (instead of opacity "hack")

Keep up the good work!