Post

🚀 Stator 1.6 is out Flaky-network resilience, built in: in-flight and connection state as data attributes, event POSTs that retry safely behind idempotency keys, and live pages that resync in place after a dropped connection — no reload. statorjs.dev #javascript #webdev #StatorJS

statorjs.devStator · the server-canonical JavaScript framework built on state machinesA web framework where state machines are the unit of composition and the DOM renders where its state lives — almost always the server.

statorjs.dev

@statorjs.dev

27 July

Loading states without state. While an event is in flight, the runtime marks the element: button[data-stator-pending] { opacity: .6 } One rule covers every button in the app. No loading flags, no disabled bookkeeping, and it clears correctly on every failure path.

statorjs.dev

@statorjs.dev

A tap on train wifi now lands. Every event carries an idempotency key. Network drops retry with backoff, and if the first attempt actually committed, the server replays the original response instead of applying it twice. A cart button that can't double-add, with no app code.

27/7/26, 4:46 am0 reposts0 likes

statorjs.dev

@statorjs.dev

27 July

Live pages heal in place. Kill the server under a live dashboard and bring it back — the SSE channel reopens and a full resync converges the DOM. Scroll, focus, and island state all survive. One attribute on <html> turns an offline banner into a CSS rule, not a component.