- env.ts: supabase: SupabaseConnection | null resolved from env.js
(supabaseUrl/supabaseAnonKey), VITE_SUPABASE_*, else null; half config refused
- lib/supabase.ts: getSupabaseClient() null when unconfigured, one client per URL
- entrypoint.sh writes the two public values; .env.example placeholders
- Dockerfile copies packages/supabase manifest for the install layer
- no UI change; 7 new tests (278 app)
semgrep HIGH: no USER directive before ENTRYPOINT (container ran as
root). Runtime dirs, conf.d and html dir chowned to nginx so the
entrypoint (env.js write + PORT envsubst) and nginx master both run
as uid 101. Verified: docker build + run, HTTP 200, SPA fallback,
env override OK, ps shows master+workers as nginx.
CONSTRAINT: PORT env var must now be >=1024 (default 8080 unaffected).
Prior pin pnpm@11.1.3 was insufficient — pnpm 11.x itself imports
`node:sqlite` and requires Node 22.13+, not just 11.4 as the previous
blocker entry assumed. Local builds passed only because no `pnpm
install` ran on Node 20 (lockfile already resolved). VPS cold build
still crashes `ERR_UNKNOWN_BUILTIN_MODULE: node:sqlite`.
Switch to pnpm 10.13.1 — already cached on the dev host via corepack,
last major before the node:sqlite cache backend, reads lockfile v9.0
unchanged.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
`corepack prepare pnpm@latest` now resolves to pnpm >=11.4, which
imports `node:sqlite` and requires Node 22.13+. The builder stage
runs `node:20-alpine`, so the install crashes with
`ERR_UNKNOWN_BUILTIN_MODULE: node:sqlite`. Pinning to the same
version the host already uses (pnpm 11.1.3) restores a reproducible,
Node-20-safe build.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>