command-code 0.41.3 → 0.42.0

package/bin/run.mjs

@@ -0,0 +1,25 @@
+#!/usr/bin/env node
+// Launcher for the bundled CLI. Its one job: default NODE_ENV to
+// 'production' BEFORE the ESM graph loads.
+//
+// react/ink are runtime dependencies (external to the tsup bundle), and ESM
+// evaluates a module's static imports before any of its own statements — so
+// an assignment inside dist/index.mjs (or its bootstrap module) runs AFTER
+// React has already picked its build. Without this, every end user runs the
+// DEVELOPMENT react-reconciler, whose component-performance tracking records
+// a PerformanceMeasure per render with the component's props serialized into
+// the entry detail. Those entries are never cleared, pinning a copy of every
+// rendered prompt, reasoning block, and tool output for the life of the
+// session — the dominant retainer in issue #550's heap OOM (verified via
+// --heapsnapshot-near-heap-limit). An explicitly set NODE_ENV (local dev,
+// tests) is respected. The dynamic import defers evaluation until after the
+// env is set.
+if (!process.env.NODE_ENV) {
+	process.env.NODE_ENV = 'production';
+}
+// NOTE: dist/index.mjs is now itself a launcher (built from src/launcher.ts);
+// the real bundle is dist/cli.mjs. This file is retained only as a safety net
+// for installs whose bin symlink was linked to bin/run.mjs by the `npm i -g`
+// fallback path of an older auto-update, so that they keep working after they
+// atomic-update to a version where the canonical bin target is dist/index.mjs.
+await import(new URL('../dist/cli.mjs', import.meta.url));