Datastar Kit
Datastar

Playground

Three server-backed specimens.

Live interactions served straight from the server. The page you are reading is the application state.

Inline validation

Signals carry the form to the server. Zod validates on the server, and errors come back as signal patches.

Submit the form and the server validates it with Zod.

Active search

Each keystroke is debounced into a GET request. The server filters data and patches the list as HTML.

  • 200OKThe request succeeded.
  • 201CreatedA new resource was created.
  • 204No ContentSuccess with an empty body. Datastar Kit uses it for reply.done().
  • 301Moved PermanentlyThe resource has a new canonical URL.
  • 302FoundTemporary redirect to another URL.
  • 304Not ModifiedThe cached representation is still valid.
  • 400Bad RequestThe server cannot process the malformed request.
  • 401UnauthorizedAuthentication is required and has failed.
  • 403ForbiddenAuthenticated, but not allowed.
  • 404Not FoundNo resource lives at this URL.
  • 409ConflictThe request conflicts with the current state.
  • 418I'm a teapotThe server refuses to brew coffee in a teapot.
  • 422Unprocessable ContentWell-formed, but semantically invalid.
  • 429Too Many RequestsThe client is being rate limited.
  • 500Internal Server ErrorSomething failed on the server.
  • 503Service UnavailableThe server is temporarily overloaded or down.

Browser-only signals

Some state never needs a round trip. These expressions stay in the browser and still start from server-rendered HTML.

Want more? The repository ships fourteen runnable examples covering todos, realtime counters, modals, and a Linear-style issue tracker.