fuz_util

utilities ยท ready ยท TypeScript ยท util.fuz.dev

fuz_util 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.

The coherence and values pages do not yet name this project.

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
fuz_app peerpackage.json@fuzdev/fuz_util
fuz_blog peerpackage.json@fuzdev/fuz_util
fuz_code peerpackage.json@fuzdev/fuz_util
fuz_css peerpackage.json@fuzdev/fuz_util
fuz_repos peerpackage.json@fuzdev/fuz_util
fuz_ui peerpackage.json@fuzdev/fuz_util
gro peerpackage.json@fuzdev/fuz_util
mdz peerpackage.json@fuzdev/fuz_util
zzz peerpackage.json@fuzdev/fuz_util
blake3 devpackage.json@fuzdev/fuz_util
corpora devpackage.json@fuzdev/fuz_util
fuz-stack (docs.fuz.dev)devpackage.json@fuzdev/fuz_util
fuz_forge devpackage.json@fuzdev/fuz_util
fuz_schema devpackage.json@fuzdev/fuz_util
fuz_template devpackage.json@fuzdev/fuz_util
pglet devpackage.json@fuzdev/fuz_util
svelte-docinfo devpackage.json@fuzdev/fuz_util
tsv devpackage.json@fuzdev/fuz_util
tsv (tsv.fuz.dev)devpackage.json@fuzdev/fuz_util
zap devpackage.json@fuzdev/fuz_util

What it uses

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

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: esm-env
optional peer
package.json: @types/estree, @types/node, svelte

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

How its CLAUDE.md comments its check command:

  • gro check  # typecheck, test, lint, format check (run before committing)
    line 14, marked as the command to run before committing

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

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.

Gates

  • Types, tests, lints and format (every change): Type errors, regressions, lint errors and style drift. fuz_util 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_util 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_util 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_util 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_util 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.