fuz_app

fullstack ยท early ยท TypeScript ยท app.fuz.dev

fuz_app as this site sees it: what its repo's own files declare, and every record on the coherence and values pages that names it or links it. This page is computed and adds nothing of its own. For what the project is, see the Fuz stack page.

What uses it

The stack repos that declare a dependency on it. A breaking change has to be carried through each of them, and through any consumer that no manifest declares. Only the stack's own projects are listed, so a consumer outside the stack is not here.

Used byKindDeclared inThrough
zzz peerpackage.json@fuzdev/fuz_app
fuz_forge devpackage.json@fuzdev/fuz_app

What it uses

UsesKindDeclared inThrough
blake3 peerpackage.json@fuzdev/blake3-wasm
fuz_schema peerpackage.json@fuzdev/fuz_schema
fuz_util peerpackage.json@fuzdev/fuz_util
fuz_css optional peerpackage.json@fuzdev/fuz_css
fuz_ui optional peerpackage.json@fuzdev/fuz_ui
pglet optional peerpackage.json@fuzdev/pglet-wasm
fuz_code devpackage.json@fuzdev/fuz_code
gro devpackage.json@fuzdev/gro
mdz devpackage.json@fuzdev/mdz
svelte-docinfo devpackage.jsonsvelte-docinfo

Read from the repos' manifests on . Only each repo's root manifests are read. A manifest shows what a repo declares, which is not always what its code imports, and a dependency that no manifest states, such as a sibling checkout a test reads, is not here. The kind is the manifest table a dependency is declared in, not how much it matters: an app that bundles what it builds declares everything as dev. See every dependency in the stack.

What it declares from outside the stack

peer
package.json: @sveltejs/kit, svelte
optional peer
package.json: @electric-sql/pglite, @hono/bun, @hono/node-server, @node-rs/argon2, esm-env, hono, pg, ws

Read from the repo on . What a repo's manifests declare from outside the stack, by name and without versions. The dev tables are left out, so what an app bundles from its dev table is not here. For a Cargo workspace the list is every crate's together, and it is what is declared, not what a release build links. A crate is left out as tooling only when it is named xtask or testing_*, or the release audit marks it dev-only, so what a bench, debug or test-support crate under another name uses is listed with the rest. See everything the stack declares.

Its check script and CI

The check script of its package.json:

gro check

Its CLAUDE.md has no line in a code block that gives gro check or npm run check with a # comment, and none whose comment says to run it before committing. It may describe its checks another way.

It is among the repos whose check script runs gro check; with a CI step, on a push or a pull request, that runs gro check with --workspace; with an exports map in package.json, and a CI step, on a push or a pull request, that runs gro check with --workspace; with a CI step, on a push or a pull request, that runs gro check with --build.

.github/workflows/check.yml runs on push (branches main), pull_request (branches **), workflow_dispatch

build on ubuntu-latest

  1. uses actions/checkout, pinned to a commit
  2. Use Node.js ${{ matrix.node-version }}
    uses actions/setup-node, pinned to a commit
  3. npm ci
  4. npx @fuzdev/gro check --workspace --build

cross-ts on ubuntu-latest

  1. uses actions/checkout, pinned to a commit
  2. Use Node.js 24.14
    uses actions/setup-node, pinned to a commit
  3. Install Bun
    curl -fsSL https://bun.sh/install | bash -s "bun-v$CROSS_BUN_VERSION"
    echo "$HOME/.bun/bin" >> "$GITHUB_PATH"
  4. Verify runtime versions
    node --version
    bun --version
    [ "$(bun --version)" = "$CROSS_BUN_VERSION" ]
  5. npm ci
  6. npx svelte-kit sync
  7. npm run test:cross:ts
  8. npm run test:cross:ts-differential
.github/workflows/cross-canary.yml runs on schedule (at 17 6 * * 1), workflow_dispatch

latest-runtimes on ubuntu-latest

  1. uses actions/checkout, pinned to a commit
  2. Use Node.js 24.14
    uses actions/setup-node, pinned to a commit
  3. Install Bun (latest)
    curl -fsSL https://bun.sh/install | bash
    echo "$HOME/.bun/bin" >> "$GITHUB_PATH"
  4. Show runtime versions
    node --version
    bun --version
  5. npm ci
  6. npx svelte-kit sync
  7. FUZ_TEST_CROSS_BACKEND=1 npx vitest run --project cross_backend_ts_bun --project cross_backend_ts_differential

Read from the repo on . A workflow's jobs and steps are as the file writes them: a step's command, or the action it uses without its version. An action's inputs, a matrix's values, permissions, environment and working directories are left out, and nothing here says which command is the gate. A line is quoted when it sits in a code block of the repo's CLAUDE.md, has a # comment after the command, and either is the command gro check or npm run check, or has a comment that says to run it before committing. A repo that describes its check command in a sentence or a list, or in another file, has no line here. Every file is read at the repo's main branch as the checkout last fetched it, so nothing uncommitted or unpushed is here. See every repo's checks.

Holds that name it

Comparisons that name it

ComparedAgainstKindRunsSource
fuz_app backend on NodeThe same backend on BunBuild
CI
cross-backend tests
fuz_app backend, TypeScriptThe fuz spine crates, RustTwin
On demand
cross-backend tests
zzz serverfuz_app's shared cross-backend suitesSuite
On demand
development stage

From Oracles in use.

Gates

  • Types, tests, lints and format (every change): Type errors, regressions, lint errors and style drift. fuz_app is among the repos whose check script runs gro check.
  • Drift in generated files (every change): A generated file that no longer matches its source. fuz_app is among the repos whose check script runs gro check.
  • Drift in the package exports map (ci): An exports map that no longer matches the source, which the local gate rewrites instead of failing on. fuz_app is among the repos with an exports map in package.json, and a CI step, on a push or a pull request, that runs gro check with --workspace.
  • Build (ci): A broken build. fuz_app is among the repos with a CI step, on a push or a pull request, that runs gro check with --build.
  • A clean tree after the run, and no TODO docs at the root (ci): Uncommitted output and a TODO Markdown file at the repo root. fuz_app is among the repos with a CI step, on a push or a pull request, that runs gro check with --workspace.

From Gates. A gate is listed here when its row names the project or links its repo, or speaks of a class of repos that the snapshot puts this one in.

Rules that moved down

  • State a new mount flag in every test server config became: Mount flags with no default, so the typecheck names any that a config leaves out.

From Rules that moved down.

Values

  • A decision: security over speed. A login for an unknown account still verifies a dummy password hash, so its timing matches a wrong password. Cost: A password hash verified on every login for an unknown account. security
  • Passes the question of security: fuz_app's composable suites, which give an app built on it the attack-surface, adversarial-header, rate-limiting and data-exposure tests that fuz_app runs on itself
  • Passes the question of security: fuz_app's cross-backend tests, where one set of security cases, among them the credential ceiling, the privilege gates and login enumeration, runs over the wire against each backend
  • Passes the question of security: fuz_app's security reference, which names the attackers its auth stack is designed against

From the values page.