Follow-up from PR #122 (raised in the batch implementation and in two external reviews).
Next.js output file tracing pulls repo-root extras (docs/, charts/, e2e/, CLAUDE.md, bun.lock) into the standalone output, inflating every payload-derived artifact: the tarballs, the .deb/.rpm (~78 MB package, ~240 MB installed), the snap, and the npx cache.
Proposal:
- Add outputFileTracingExcludes to next.config for the known non-runtime directories, and/or prune the payload in scripts/build-standalone-payload.sh (single source used by CI and local builds).
- Target: roughly halve the payload; verify with the script's --smoke boot and the existing zero-env login flow.
- Watch for under-exclusion regressions: better-sqlite3 bindings and @libredb/libredb must stay in.
Note: local (non-CI) builds also traced gitignored root files before; releases are unaffected because CI checkouts are clean, but pruning fixes local builds too.
Follow-up from PR #122 (raised in the batch implementation and in two external reviews).
Next.js output file tracing pulls repo-root extras (docs/, charts/, e2e/, CLAUDE.md, bun.lock) into the standalone output, inflating every payload-derived artifact: the tarballs, the .deb/.rpm (~78 MB package, ~240 MB installed), the snap, and the npx cache.
Proposal:
Note: local (non-CI) builds also traced gitignored root files before; releases are unaffected because CI checkouts are clean, but pruning fixes local builds too.