[RohanReddy44]

The tail of #13. Those three commits were pushed after it merged, so they missed it.

Bun → Node and npm

Bun was chosen because npm could not install this tree at all, crashing with Cannot read properties of null (reading 'edgesOut').

That was one dependency, not the tree. npm installs cleanly with vitest removed and crashes in #loadPeerSet with it present — vitest 4 declares a large optional-peer set npm's arborist cannot walk. Vitest 5 does not have the problem, so the fix is an upgrade rather than a workaround.

What forced the question was the container build failing with Cannot find package 'tsx:'. vite.config.ts passes virtualRouteConfig as a path, so the router generator loads that TypeScript file through tsx — a Node loader. The fix on Bun was to install Node beside it: two runtimes to work around one plugin. It also failed only intermittently, depending on whether the generator's cache re-ran, so the build worked on one machine and not the next.

Nothing runs a JavaScript runtime in production — the artifact is static files behind nginx — so this is a build-time choice only.

Two things npm surfaced that Bun had absorbed silently:

• @vitest/coverage-v8 was pinned to 4.0.17 against vitest@^4.1.11, a real conflict
• vitest 3 would also have installed, but carries a moderate path-traversal advisory covering 2.1.0-beta.1–4.1.10. Downgrading would have added a vulnerability

No --legacy-peer-deps anywhere: it hides exactly this kind of conflict. packageManager, the Dockerfile, CI, the hooks and the docs all follow.

Dead code

A whole-graph sweep. Unused exports 35 → 20, unused types 7 → 0; the 20 remaining are all vendored shadcn kept as a complete API, which tree-shaking drops from the bundle anyway.

• The recording half of audio-utils.ts was dead — no callers, and removing it orphaned four private helpers and an interface in turn. 374 lines → 93. Playback survives
• The per-screen query layer was empty scaffolding — export const ChatScreenQueries = {} as const with a TODO, behind two barrels and a misspelled componets/ directory. The queryClient and its MutationCache stay; that part is real, and it is where the first thing needing caching or invalidation plugs in
• OnRequestError was a React component returning an empty <div>, used as a MutationCache onError callback. Only the logging ever had an effect
• Telemetry left two modules and a 648 KB dependency behind — getBrowserInfo, getFingerprintId and @fingerprintjs/fingerprintjs
• ConfigProvider's React context had no consumer — nothing called useConfig, since everything reads getConfig() directly. The effect that applies theme variables remains, which was always its real job
• The screen-scaffold generator, 250 lines, whose default parent was app/(_authenticated) — a route group deleted with sign-in, so its output would not have compiled

Net −439 / +38 across 20 files.

Verified

Clean worktree with npm ci: lint, typecheck, knip, 23 tests, coverage, build, route-tree guard. The image builds --no-cache on node:22-alpine and serves — routes fall back, missing files 404, config.json is no-store, and the app renders under a strict CSP.

🤖 Generated with Claude Code