Type Alias JssmGenericConfig<StateType, DataType>

Maximum depth of the boundary-hook action cascade before the machine throws a jssm_error!JssmError rather than risking a stack overflow or hang.

Each time a boundary action fires a transition that itself crosses a boundary, the depth counter increments. A cascade exceeding this limit is treated as a probable infinite loop and rejected.

Defaults to 100. Raise it for legitimate pipelines that genuinely nest more than 100 transitions via boundary hooks.

Cancels a timer previously scheduled by timeout_source. Defaults to clearTimeout.

Overlapping-state-group tables produced by the compile pass and consumed by the Task-3 runtime cascade.

group_registry maps each group name to its ordered list of direct members (states and sub-group references) as declared in the FSL source.

group_metadata maps each group name to its RAW style object { declarations: [...] } — parsed style items from a state &g : { … }; declaration, not condensed JssmStateConfig style fields. Condensation is intentionally deferred to the Task-3 runtime cascade so that depth-specificity resolution can weight each group's contribution before merging into per-state config.

group_hooks and state_hooks hold boundary-hook payloads keyed by group name and state name respectively; firing is also a Task-3 concern.

All four fields are absent (undefined) on machines that declare no groups or hooks.

Schedules fn to run after delay_ms, and returns a handle that will be handed back to clear_timeout_source untouched. Defaults to setTimeout.

The handle is typed number — the browser shape. Node's setTimeout returns a Timeout object instead, so a Node-shaped source casts it (as jssm's own DEFAULT_TIMEOUT_SOURCE does); jssm never inspects the handle, it only stores it and gives it back.

(Before 5.162.14 these read (Function, number) => number, in which Function and number were parameter names, not types — so both parameters were silently any.)