statorjs.dev

Confirmed: version numbers really are cheap 🏷️ #StatorJS 2.5 is out 🚀 five minors since 2.0. Each one small, but together they round out what production apps need: real security primitives, first-party middleware, and a CLI that owns the toolchain. statorjs.dev

2.5 itself adds the seam the CLI made necessary: boot.ts. defineBoot hosts server-lifetime work, query config at startup, run the poll or subscription that feeds your machines, tear down on shutdown. Boot is a source, not a controller. Policy stays in the machine, where it's testable.

Confirmed: version numbers really are cheap 🏷️ #StatorJS 2.5 is out 🚀 five minors since 2.0. Each one small, but together they round out what production apps need: real security primitives, first-party middleware, and a CLI that owns the toolchain. statorjs.dev

Middleware is a file, not config. middleware.ts covers every route by position, and the framework's security defaults always run first. Stator's built-in CSRF guard was the proving case: it's now crossSiteGuard(), first-party middleware alongside cors() and securityHeaders().

Confirmed: version numbers really are cheap 🏷️ #StatorJS 2.5 is out 🚀 five minors since 2.0. Each one small, but together they round out what production apps need: real security primitives, first-party middleware, and a CLI that owns the toolchain. statorjs.dev

Stator 2.0 is out 🎉 🌶️ We removed two-way binding read() is now the only display primitive. Its the same in a server template or a client island - the compiler picks the right mechanism for each. Writes are typed events that machines declares and the compiler checks statorjs.dev #StatorJS #webdev

Forms without a binding layer: The input owns your draft, with cursor, IME, and undo all native. A typed event commits it, and a refused commit keeps your typing. Pre-fill is just server rendering: value and checked are attributes, and false renders absent. No echo loop to manage.

Stator 2.0 is out 🎉 🌶️ We removed two-way binding read() is now the only display primitive. Its the same in a server template or a client island - the compiler picks the right mechanism for each. Writes are typed events that machines declares and the compiler checks statorjs.dev #StatorJS #webdev

Stator 1.7 is out 🚀 Stator renders your pages on the server, straight from the state machines that hold your logic. As of today those same machines can serve your JSON API, your RSS feed, and anything else that speaks HTTP. No second data layer, nothing to keep in sync. statorjs.dev

APIs can be viewer-aware too. The with-auth example serves its notice board at /api/notices, where members see everything and visitors only the public notices. Identity comes from the session's own auth machine rather than the request, so there's nothing in a payload to forge.

Stator 1.7 is out 🚀 Stator renders your pages on the server, straight from the state machines that hold your logic. As of today those same machines can serve your JSON API, your RSS feed, and anything else that speaks HTTP. No second data layer, nothing to keep in sync. statorjs.dev

A consumer API used to mean a second data path beside your pages. In 1.7 it's one route file: export a GET, read your machines, return a value, and Stator serves it as JSON with an ETag. What the page shows and what the API returns can't drift, they're read from the same state.

🚀 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

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.

🚀 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

Stator 1.4 is out 🎉 Stator keeps your app state on the server — the browser just gets tiny DOM patches. New: defer() for slow APIs — fetches run in parallel and the page arrives complete. And live lists that update one field at a time. statorjs.dev #StatorJS #webdev

Ever had a live list flicker, or eat someone's focus mid-type? Stator rows update one field at a time. A vote comes in - the count and the bar move, nothing else does. Someone can be typing in one row while the rest keep updating around them.

Stator 1.4 is out 🎉 Stator keeps your app state on the server — the browser just gets tiny DOM patches. New: defer() for slow APIs — fetches run in parallel and the page arrives complete. And live lists that update one field at a time. statorjs.dev #StatorJS #webdev

Ever built a page that's mostly loading-state plumbing? With defer() you write the fetch and an HTML arm for the result. Every defer on the page runs in parallel - three slow APIs cost you the slowest one, not the sum. Failures get a fallback you wrote. No spinners to manage.