- docs/plan/16-toolchain-2026.md: the assessment - what each release
changes, what was measured here, the decisions, how to move each runtime
next time, and what was left.
- docs/plan/17-typescript-7.1.md: the springboard for dropping TypeScript 6
once 7.1 ships - start conditions and how to check them, the steps, the
planted-error table and the baselines to compare against.
- CLAUDE.md: "TypeScript is two packages, on purpose" and "One version of
each runtime"; the uv compile line says 3.15.
- dev_env (EN/VI), README, AUTHORS, TAURI.md, web/README, THIRD_PARTY,
DEPLOYMENT (Workers Builds' NODE_VERSION=26, the Checks paragraph),
ACKNOWLEDGEMENTs and the About page's stack list ("TypeScript 7 + 6").
- CHANGELOG: the Tooling entry.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
3.2 KiB
Third-Party Dev Tooling
Dev-time tools the project depends on for dead-code detection, linting, and dependency auditing. None of these ship in the data pipeline, the web bundle, or the desktop app — they only run on a maintainer's machine before a release.
Runtime dependencies (the libraries that actually ship) live in
ACKNOWLEDGEMENTs.md and the in-app
About → Stack & third-party section.
Dead-code & audit tools
Added in v3.2.7 to make the pre-publish checks below runnable.
| Tool | Scope | Purpose | License |
|---|---|---|---|
| knip | Web app (web/) |
Finds unused files, exports, types, enum members and dependencies across the SvelteKit app, the Worker and the admin build. | ISC |
| vulture | Python pipeline (scripts/) |
Finds unused functions, classes, variables, imports, and unreachable code. | MIT |
| pip-audit | Python pipeline | Audits the pinned Python dependencies against the OSV / PyPI Advisory vulnerability databases. | Apache-2.0 |
| svelte-check | Web app (web/) |
Type-checks .svelte files, which tsc cannot read. Runs twice in npm run typecheck — once for the app, on TypeScript 7 (--tsgo), and once for the admin build, on TypeScript 6 (--tsgo cannot follow its imports from ../src). |
MIT |
| vitest | Web app (web/) |
The test runner behind npm test. |
MIT |
Where they're declared
- knip —
web/package.jsondevDependencies; config in../web/knip.json. - vulture + pip-audit —
../requirements-dev.txt; vulture config in../pyproject.tomlunder[tool.vulture].
Install the Python dev tools with pip install -r requirements-dev.txt from the
repo root, in a pip call of its own: requirements.txt and
requirements-test.txt (what CI installs, pytest included) carry hashes, and a
pip call that reads a hashed file wants a hash for every package. The web
tooling arrives with npm install inside web/.
Pre-publish checks
Run this suite from a clean checkout before tagging / re-publishing a release, and fix every error before continuing.
Web — from web/:
npm run knip # dead code: unused files / exports / deps
npm run typecheck # svelte-check + tsc strict, app / admin / Worker / tests
npm test # vitest
npm run build # full production build must pass
npm audit # dependency CVEs
npm run typecheck and npm run build both run build:admin first, because
worker/index.ts imports the generated admin bundle. That is deliberate — a
bare tsc or wrangler deploy without it is supposed to fail.
Python — from the repo root:
vulture scripts/ # dead code
pip-audit -r requirements.txt # dependency CVEs
A confirmed false positive belongs in the tool's ignore config — ignore /
ignoreDependencies in web/knip.json, or a higher min_confidence /
whitelist for [tool.vulture] in pyproject.toml — never suppressed silently.