Alpine.js v3 Requires x-data as Function Instead of Plain Object

The goal is to quantify any initialization overhead introduced by the mandatory function syntax for x-data in Alpine.js v3 compared to the plain‑object syntax accepted in v2.

Because v3 no longer accepts plain objects, a direct comparison requires either a compatibility wrapper that converts a plain object to a function or running Alpine v2 alongside v3, which may introduce additional variables. This makes it unclear whether observed timing differences stem from the function wrapper itself or from the shim/v2 interaction.

• What is the measurable difference in component initialization time between x-data defined as a function returning an object and a plain‑object shim in Alpine.js v3?
• Does this overhead increase proportionally with the size or complexity of the initial state object?
• Are there any hidden costs in the reactivity system attributable to the function wrapper that could affect subsequent state updates?