Live scenario
Observable state editor
- Model
Object updates, deep mutation events, reset, destroy, and reuse.
- Operations
- 0
- Events
- 0
- Renders/routes
- 0
- Last run
- —
Compatibility lab
This page runs bounded, deterministic browser scenarios across every non-empty combination of Model, Mediator, View, and Router. Each card can run normally, execute a 1000-operation stress pass, reset, and destroy.
The public controls are intentionally safe for a static site. More aggressive Node.js request-isolation and lifecycle stress cases run in CI instead of exposing a public load endpoint.
Live scenario
Object updates, deep mutation events, reset, destroy, and reuse.
Live scenario
Publish, subscribe, cancellation, listener cleanup, and reuse.
Live scenario
Template rendering, delegated events, root replacement, and teardown.
Live scenario
Route matching, query parsing, programmatic navigation, and rejection-safe state.
Live scenario
Namespaced Model events relayed through a standards-based mediator.
Live scenario
Model-driven rendering with View-owned interaction and repeated rerendering.
Live scenario
Router query state translated into observable application state.
Live scenario
Independent application events drive a View without a state package.
Live scenario
Navigation intent crosses the mediator/router structural event boundary.
Live scenario
Routes switch View output while preserving explicit lifecycle ownership.
Live scenario
View interaction mutates Model state while Mediator observes relayed changes.
Live scenario
Route intent updates session state and publishes namespaced state events.
Live scenario
URL query data drives Model state and reactive View output.
Live scenario
Router intent emits application events consumed by an independent View.
Live scenario
Router → Model → Mediator → View plus View-owned navigation interaction.
Live scenario
Repeated nested writes verify mutate paths and detached-state behavior.
Live scenario
Many simultaneous listeners exercise synchronous dispatch and cleanup.
Live scenario
Animation-frame batching coalesces repeated observable change events.
Live scenario
Rejected guarded navigation must preserve the last successful route state.
Live scenario
Repeated create/run/destroy cycles hunt leaked listeners and cross-instance state.