Race condition in multiple use: action execution order

Svelte Action Sequencing

Svelte allows multiple use: actions to be attached to a single DOM element to encapsulate reusable behavior. These actions are executed when the element is mounted to the DOM, providing a mechanism to interact directly with the underlying node.

A potential conflict arises when multiple actions are applied to the same element and depend on a specific initialization sequence. If one action modifies a property or attaches a listener that a subsequent action must interact with, the lack of an explicitly documented execution order creates uncertainty regarding stability across compiler versions.

Given that actions can modify the same element attributes or share a global context, the precise sequence of execution is critical for avoiding state inconsistencies.

• Does Svelte guarantee that actions are executed in the order they are declared in the markup?
• Is there a documented mechanism to enforce a specific dependency order between multiple actions on one element?