CDN · SQLite WASM

Durable Objects in your browser

Run durable actors in a browser module worker. State lives in OPFS, survives reloads, and can be shared safely by every tab on the same origin.

Read the five-minute guide

Actor class chat-room.js

class ChatRoom extends Actor {
  static actorType = "ChatRoom"
  messages = []

  post({ user, text }) {
    const message = { user, text, sentAt: Date.now() }
    this.messages = [...this.messages, message].slice(-50)
    return message
  }
}

await ChatRoom.ref("lobby").post({
  user: "Ada",
  text: "Hello from tab A",
})

Every tab posts to the same room identity. Messages commit in order and survive a reload in shared SQLite.

No package manager worker.mjs

import {
  Actor,
  configure,
  sharedSqliteWasm,
} from "https://esm.sh/solid-objects@0.14.3/browser/host"

const runtime = configure({
  database: sharedSqliteWasm({ path: "app.db" }),
  authorizeMessage: () => true,
  authorizeQuery: () => true,
})

await runtime.install()

Pin the version. Allow https://esm.sh and 'wasm-unsafe-eval' in your Content Security Policy.

Paste into your coding agent reckless-audit.txt

Find genuinely load-bearing opportunities
for the solid-objects npm library in-browser features.

Return five real cross-tab races,
restart-doomed timers, trusted room IDs,
or local state doing a server's job.

Give file:line and the browser actor fix.
Invent nothing. Admit when a transaction or
Web Lock is less dramatic.

The agent must cite code. Vibes do not count as architecture.