mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-11 13:52:20 +00:00
/insights/mood was on its 460 KB ceiling. The route paints a calendar, a line chart, a target card and an assessment; under them sit a dozen breakdown cards — both tag axes, the influence board, the two crosstabs, the day-context comparison, four Recharts mini-charts, the correlation cards — and every one of them was a static import, so a cold mount paid for all of it before painting anything. The cluster is its own module now, loaded through next/dynamic with a skeleton, the way the insights mother page already treats its below-the-hero blocks. It takes the resolved aggregate as a prop rather than running a second query, so it cannot draw a different snapshot from the regions above it. The better-days card follows, for one specific reason: it resolves catalogue tag icons, and that resolver statically imports about a hundred and sixty lucide icons. The card sits a screen down and the map now rides the same lazy group as the breakdowns. Only mood-only modules moved. Deferring the shared target and assessment cards was tried and reverted: it bought ten kilobytes on this route and cost thirty-three on the whole-build total, because both are imported by a dozen other insight routes and a route-local lazy group duplicates them. /insights/mood 459 -> 451 KB gz (budget 460, unchanged) total client JS 3296 -> 3297 KB gz (budget 3310, unchanged) The payload shape and the section card frame move to a shared module both halves import; the two structural tests that read the old file now read the union of the two, so a guard cannot go quiet by pointing at the wrong half.
src/
Application source. HealthLog is a Next.js 16 App Router project (output: "standalone", React 19, TypeScript strict). The path alias @/* resolves to this directory. Everything a request touches lives under here; the layout below follows the request flow rather than alphabetical order.
Request flow
client → src/proxy.ts → src/app/<route>/route.ts → src/lib/api-handler.ts → handler body → src/lib/api-response.ts → client
proxy.ts— the HTTP edge (Next.js 16's renamedmiddleware). Public-path allowlist, demo-mode mutation block, server-side onboarding redirect, worker-only refusal,x-request-id+ CSP nonce generation, every security header.app/— App Router pages (RSC by default) and API routes. Every API route wraps its handler inapiHandler. Seeapp/README.md.lib/— the server/runtime toolkit:apiHandler, auth, crypto, rollups, AI, notifications, pg-boss jobs, integrations, rate limiting. Seelib/README.md.components/— React components (shadcn/ui new-york, kebab-case files). Seecomponents/README.md.
Other directories
hooks/— shared React hooks (use-prefix, kebab-case).types/— shared TypeScript declarations.generated/prisma/— the generated Prisma client (do not edit; regenerated byprisma generate). Imported as@/generated/prisma.instrumentation.ts— Next.js startup hook; boots the pg-boss worker registry and boot-time backfill queues.__tests__/— cross-cutting unit tests; most tests live in__tests__/folders next to the code they cover.
Conventions
See ../CLAUDE.md for the full set. The load-bearing ones: RSC by default ("use client" only when a hook/state/browser API needs it); every API route wraps apiHandler and parses its body with Zod safeParse; userId is always narrowed from session or Bearer, never accepted as a body field; TanStack Query keys come only from src/lib/query-keys/; outbound HTTP goes through src/lib/safe-fetch.ts.