@naarang/ccc 3.3.0-beta.13 → 3.3.0-beta.15

package/dist/scripts/build-binaries.ts

@@ -525,22 +525,22 @@ for (const { name, target, outfile, ptyLib, ngrokLib, ngrokPkg } of selectedTarg
 
     // Build the binary (bun-pty and ngrok are now bundled via the generated loaders).
     //
-    // --bytecode is safe again on Linux/macOS — it previously broke
-    // the Pi SDK loader (oven-sh/bun#6893, #11732) but the loader
-    // now uses static imports of a bundled Pi so resolution happens
-    // at build time. Bytecode caching => faster startup.
-    //
-    // On Windows, --bytecode + --compile triggers a Bun internal
-    // panic ("Internal assertion failure: total_insertions ... !=
-    // output_files.items.len ..."). Tracked in oven-sh/bun#23490
-    // and elsewhere; intermittently reintroduced across Bun
-    // releases. Skip --bytecode on Windows to keep the build green.
-    const useBytecode = !target.startsWith('bun-windows');
+    // --bytecode is disabled across all targets — Bun 1.3.13 has
+    // multiple regressions when combined with --compile:
+    //   - Windows panics: "Internal assertion failure:
+    //     total_insertions != output_files.items.len"
+    //     (oven-sh/bun#23490)
+    //   - Linux ARM64 binary loads but throws on first import:
+    //     "TypeError: Expected CommonJS module to have a function
+    //     wrapper" — bytecode mangles CJS-shaped deps (some of
+    //     pi-coding-agent's transitive deps are CJS).
+    // The startup speedup isn't worth shipping a broken binary on
+    // any platform. Re-enable per-target when Bun's bytecode +
+    // CJS interop stabilizes.
     const buildArgs = [
       'build',
       '--compile',
       '--minify',
-      ...(useBytecode ? ['--bytecode'] : []),
       `--target=${target}`,
       '--define',
       `BUILD_VERSION="${VERSION}"`,

package/dist/scripts/build-dist.ts

@@ -20,7 +20,13 @@ if (existsSync(distDir)) {
 
 // Build with version define
 try {
-  await $`bun build src/index.ts --outdir dist --target bun --minify --external bun-pty --external expo-server-sdk --external @ngrok/ngrok --define BUILD_VERSION='"${VERSION}"'`;
+  // Mark Pi as external for the npm build. Pi 0.74+ has CJS-shaped
+  // transitive deps that break bun's bundler/bytecode pass. When
+  // installed via npm, Node's resolver finds Pi in node_modules
+  // alongside our dist/, so bundling it just adds risk for zero
+  // gain. (The compiled-binary build path can't do this — see
+  // build-binaries.ts for the trade-off there.)
+  await $`bun build src/index.ts --outdir dist --target bun --minify --external bun-pty --external expo-server-sdk --external @ngrok/ngrok --external @earendil-works/pi-coding-agent --external @earendil-works/pi-ai --define BUILD_VERSION='"${VERSION}"'`;
   console.log('✓ Built dist/index.js');
 } catch (error) {
   console.error('✗ Build failed:', error);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@naarang/ccc",
-  "version": "3.3.0-beta.13",
+  "version": "3.3.0-beta.15",
   "description": "Code Chat Connect - Control Claude Code from your mobile device",
   "type": "module",
   "main": "dist/index.js",

package/scripts/build-binaries.ts

@@ -525,22 +525,22 @@ for (const { name, target, outfile, ptyLib, ngrokLib, ngrokPkg } of selectedTarg
 
     // Build the binary (bun-pty and ngrok are now bundled via the generated loaders).
     //
-    // --bytecode is safe again on Linux/macOS — it previously broke
-    // the Pi SDK loader (oven-sh/bun#6893, #11732) but the loader
-    // now uses static imports of a bundled Pi so resolution happens
-    // at build time. Bytecode caching => faster startup.
-    //
-    // On Windows, --bytecode + --compile triggers a Bun internal
-    // panic ("Internal assertion failure: total_insertions ... !=
-    // output_files.items.len ..."). Tracked in oven-sh/bun#23490
-    // and elsewhere; intermittently reintroduced across Bun
-    // releases. Skip --bytecode on Windows to keep the build green.
-    const useBytecode = !target.startsWith('bun-windows');
+    // --bytecode is disabled across all targets — Bun 1.3.13 has
+    // multiple regressions when combined with --compile:
+    //   - Windows panics: "Internal assertion failure:
+    //     total_insertions != output_files.items.len"
+    //     (oven-sh/bun#23490)
+    //   - Linux ARM64 binary loads but throws on first import:
+    //     "TypeError: Expected CommonJS module to have a function
+    //     wrapper" — bytecode mangles CJS-shaped deps (some of
+    //     pi-coding-agent's transitive deps are CJS).
+    // The startup speedup isn't worth shipping a broken binary on
+    // any platform. Re-enable per-target when Bun's bytecode +
+    // CJS interop stabilizes.
     const buildArgs = [
       'build',
       '--compile',
       '--minify',
-      ...(useBytecode ? ['--bytecode'] : []),
       `--target=${target}`,
       '--define',
       `BUILD_VERSION="${VERSION}"`,

package/scripts/build-dist.ts

@@ -20,7 +20,13 @@ if (existsSync(distDir)) {
 
 // Build with version define
 try {
-  await $`bun build src/index.ts --outdir dist --target bun --minify --external bun-pty --external expo-server-sdk --external @ngrok/ngrok --define BUILD_VERSION='"${VERSION}"'`;
+  // Mark Pi as external for the npm build. Pi 0.74+ has CJS-shaped
+  // transitive deps that break bun's bundler/bytecode pass. When
+  // installed via npm, Node's resolver finds Pi in node_modules
+  // alongside our dist/, so bundling it just adds risk for zero
+  // gain. (The compiled-binary build path can't do this — see
+  // build-binaries.ts for the trade-off there.)
+  await $`bun build src/index.ts --outdir dist --target bun --minify --external bun-pty --external expo-server-sdk --external @ngrok/ngrok --external @earendil-works/pi-coding-agent --external @earendil-works/pi-ai --define BUILD_VERSION='"${VERSION}"'`;
   console.log('✓ Built dist/index.js');
 } catch (error) {
   console.error('✗ Build failed:', error);