sqlite-first tooling

sql that stays in charge.

sqlfu keeps schema, migrations, checked-in queries, type generation, diffing, and the browser studio aligned around real SQL files instead of another abstraction layer.

Read the docs Use the local studio

local workflow

npx sqlfu starts the local backend on localhost:56081.

local.sqlfu.dev should resolve to that local server. The browser UI talks to the backend there; the heavy client bundle stays separate from the published runtime package.

npx sqlfu

# then open
http://local.sqlfu.dev

Core Surfaces

docs

Static documentation at www.sqlfu.dev, sourced from the repo markdown and rendered for the web without rewriting the content into a second format.

backend

The UI-facing API lives in packages/sqlfu. That is the product backend end users run locally, not a sidecar hidden in the UI package.

client

packages/ui is a client-only app. React, CodeMirror, and the heavier browser dependencies stay there instead of inflating the runtime package.

Local Studio

The local studio model is intentionally boring:

run npx sqlfu inside your project
the server resolves your local sqlfu.config.ts
open local.sqlfu.dev
the browser UI talks to your local backend over /api/rpc

docs set

sqlfu
Schema Diff Model
Migration Model
UI

Static docs site for sqlfu. Local studio backend lives at local.sqlfu.dev when npx sqlfu is running.