DashboardcliSEA binary size findings and safe Node.…

SEA binary size findings and safe Node.js build flags

Category: decision
Confidence: 0.90
ID: 01a0835c-cb6b-7206-9d02-996a9f4c22b4
Project ID: c760f4f9-42b0-4ce0-b36d-6b8c38d770b2
Cross-project: No
Recalled in other projects: 1
Source session: (none)
Created: 2026-06-23 09:27:14
Updated: 2026-09-08 23:31:31

Cross-Project Recalls

ProjectHitsLast recalled
opencode-lore 8 11h ago

Content

About 94.5% of the standalone binary is Node.js. Fossilize strips the copied runtime before postject injection, reducing linux-x64 from roughly 125 MiB to 108 MiB raw and 34 MiB to 30 MiB gzip. UPX is rejected because it destroys ELF notes. The largest custom-build saving is --with-intl=small-icu (~26–28 MiB); --without-inspector, --without-amaro, --v8-disable-maglev, and --enable-lto provide smaller gains. Never use --with-intl=none, --without-ssl, --without-lief, --without-sqlite, --disable-single-executable-application, or --v8-lite-mode: they break required CLI/SEA behavior or severely hurt performance. Custom builds remain deferred because five native runners and ~3.5-hour cold builds offer poor value versus ~5-minute fossilize builds; Darwin cross-compilation from Linux is unsupported.

Move to: