A-Frame Entity-Component System: Component Initialization Order

A-Frame utilizes an entity-component system where multiple components can be attached to a single entity. According to the framework's behavior, the init() method for each component is triggered based on the declaration order within the HTML markup.

A challenge arises when two components on the same entity have mutual dependencies. If Component A requires data that is only generated during the init() phase of Component B, the current system does not provide a built-in mechanism to enforce a specific execution sequence regardless of markup order.

While using the tick event or manual sequencing are common workarounds, these methods increase boilerplate and may impact performance in complex scenes.

• Is there a documented way to define explicit component dependencies to guarantee initialization order?
• Does A-Frame provide a native lifecycle hook to synchronize state between interdependent components before the first frame renders?