zzz

apps and sites ยท experimental ยท TypeScript, Svelte, Rust

zzz 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 it uses

UsesKindDeclared inThrough
blake3 runtimepackage.json@fuzdev/blake3-wasm
fuz runtimeCargo.toml(path)fuz_actions, fuz_auth, fuz_db, fuz_http, fuz_pty, fuz_realtime, fuz_sys
fuz_repos runtimeCargo.toml(path)fuz_git, fuz_repos
fuz_app peerpackage.json@fuzdev/fuz_app
fuz_schema peerpackage.json@fuzdev/fuz_schema
fuz_ui peerpackage.json@fuzdev/fuz_ui
fuz_util peerpackage.json@fuzdev/fuz_util
fuz_code devpackage.json@fuzdev/fuz_code
fuz_css devpackage.json@fuzdev/fuz_css
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

runtime
Cargo.toml: argh, axum, blake3, deadpool-postgres, futures-util, libc, nix, notify, parking_lot, reqwest, serde, serde_json, thiserror, tokio, tokio-util, tower, tower-http, tracing, uuid
package.json: date-fns
peer
package.json: @sveltejs/kit, svelte
optional peer
package.json: esm-env

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; with a Cargo workspace at the root.

.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. cp .env.development.example .env.development
  5. cp .env.production.example .env.production
  6. npx svelte-kit sync
  7. npx @fuzdev/gro check --workspace --build

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.

In the opening of the coherence section

Two of the stack's projects are made for that reading. zzz is for reading work on the maintainer's own machine, and its projects page shows each repo's uncommitted work and its distance from origin. fuz_forge is for commits that have landed: it shows a repo's commit log and its diffs to a reader, with no pull request to approve first.

From the coherence section's index.

Comparisons that name it

ComparedAgainstKindRunsSource
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. zzz 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. zzz 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. zzz 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. zzz 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. zzz 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.