amosblomqvist
8cb5e14691
- desktop:dist cleans dist/ + .next/standalone before next build: the trace sweep was shipping the PREVIOUS build's DMG inside every new one (standalone/dist = 8.0GB inside the app; measured 7.4GB DMG → 144MB). - the same sweep shipped the repo-root auth.json (dev BYOK keys, byte-identical) in every DMG ever built — excluded in the trace and REFUSED by a new build-server.mjs guard (.env* belt-and-braces). - WARNING (next.config.ts): dir-style trace excludes (dist/** etc., "./"-anchored or not) strip server-external packages to bare package.jsons — pi-ai/pi-agent-core lost their dist/, the packaged server 500'd on ERR_MODULE_NOT_FOUND. Only the three verified-safe entries stay. - new scripts/smoke-server.mjs gates desktop:dist between payload curation and packaging: boots the standalone exactly as the Electron shell does (temp LH_DATA_DIR, empty auth) and requires 200s on / + graph/models/settings. Caught both defects above on its first day. - entitlements: allow-unsigned-executable-memory dropped (2019-era relic per current electron-builder docs; weakens hardened runtime). - pi-ai + pi-agent-core pinned exact 1.0.2 — persisted chat records carry their wire shapes; post-release a bump is a migration event. Gates: typecheck, lint, 1459/1459 tests, full desktop:dist + smoke PASS.
72 lines
3.6 KiB
TypeScript
72 lines
3.6 KiB
TypeScript
import type { NextConfig } from "next";
|
|
|
|
const nextConfig: NextConfig = {
|
|
// Desktop target (Electron wrapper, 2026-09-17): standalone output = a
|
|
// self-contained .next/standalone/server.js the Electron shell spawns
|
|
// on 127.0.0.1. Harmless for plain web deploys (extra build output).
|
|
// The manual copies the docs require — public/ and .next/static — are
|
|
// done by scripts/build-server.mjs.
|
|
output: "standalone",
|
|
// SAFETY (empirically verified 2026-09-17): without this, output file
|
|
// tracing sweeps the repo's real data/ — chat records, graph ledgers —
|
|
// INTO the standalone bundle. A shipped desktop app would carry the
|
|
// developer's session data inside it.
|
|
//
|
|
// SECRETS (2026-10-08, caught in the payload audit): the same sweep
|
|
// ships the repo-root auth.json — the DEV BYOK key store — byte-identical
|
|
// into the DMG (the packaged app never reads it: the shell passes
|
|
// LH_AUTH_FILE → userData). Excluded here; build-server.mjs also REFUSES
|
|
// to package any standalone still containing it. .env* belt-and-braces
|
|
// the same class (not observed swept, same seam).
|
|
//
|
|
// ⚠ EXCLUDE PATTERNS ARE LOAD-BEARING IN WAYS THE DOCS DON'T DESCRIBE
|
|
// (empirically established 2026-10-08): adding dir excludes like
|
|
// "dist/**/*" / "./dist/**/*" for repo-root output dirs STRIPPED THE
|
|
// server-external packages (pi-ai / pi-agent-core lost everything
|
|
// under their dist/ — the traced copy collapsed to a bare package.json
|
|
// and the packaged server died on ERR_MODULE_NOT_FOUND; openai/
|
|
// @anthropic-ai — pi-ai's deps — vanished from the trace entirely).
|
|
// Anchored "./"-prefixed forms behave the same. Only the three entries
|
|
// below are verified safe (complete externals trace + clean payload).
|
|
// The 7.4 GB recursive-DMG payload (repo dist/ swept into the bundle,
|
|
// shipping the previous build inside the next) is instead prevented by
|
|
// the `rm -rf dist .next/standalone` clean step in desktop:dist —
|
|
// verified sufficient, since the sweep can only copy what exists at
|
|
// trace time. scripts/build-server.mjs guards the rest.
|
|
outputFileTracingExcludes: {
|
|
"*": [
|
|
"data/**/*",
|
|
"auth.json",
|
|
".env*",
|
|
],
|
|
},
|
|
// Empirically verified gaps (2026-09-17 standalone smoke): the tracer
|
|
// misses JSON loaded via `import ... with { type: "json" }` attributes —
|
|
// pi-ai's provider catalog (39 JSON files) vanished from the trace and
|
|
// the server 500s on module load. Include the whole data dirs of the
|
|
// runtime-loaded engine packages.
|
|
// pdfjs-dist (sources v0 live smoke, 2026-09-19): its legacy build loads
|
|
// the node fake worker (pdf.worker.mjs) and our standard_fonts dir via
|
|
// runtime-resolved paths — invisible to the tracer. Bundling (without
|
|
// serverExternalPackages below) additionally breaks the worker's
|
|
// import.meta.url resolution inside .next/dev chunks — the live smoke
|
|
// caught it; unit tests run unbundled and never see it.
|
|
outputFileTracingIncludes: {
|
|
"*": [
|
|
"node_modules/pdfjs-dist/legacy/**/*",
|
|
"node_modules/pdfjs-dist/standard_fonts/**/*",
|
|
"node_modules/@earendil-works/pi-ai/dist/providers/data/**/*",
|
|
"node_modules/@earendil-works/pi-agent-core/dist/**/*.json",
|
|
],
|
|
},
|
|
// Framework-free core lives in src/ (plain TS, imported by routes and CLI alike).
|
|
// The pi engine must stay external: its providers are runtime-loaded Node
|
|
// code (undici streams, catalog data) that breaks when bundled into routes.
|
|
serverExternalPackages: [
|
|
"@earendil-works/pi-ai",
|
|
"@earendil-works/pi-agent-core",
|
|
"pdfjs-dist", // sources v0: bundling breaks its node fake-worker path
|
|
],
|
|
};
|
|
|
|
export default nextConfig; |