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

package/dist/scripts/build-binaries.ts

@@ -525,17 +525,30 @@ for (const { name, target, outfile, ptyLib, ngrokLib, ngrokPkg } of selectedTarg
 
     // Build the binary (bun-pty and ngrok are now bundled via the generated loaders).
     //
-    // Note: deliberately NOT using --bytecode. Bytecode compilation
-    // freezes module resolution at build time, which breaks dynamic
-    // `import()` of absolute file:// URLs that have their own
-    // transitive deps (see oven-sh/bun#6893, #11732). The Pi SDK
-    // loader does exactly this — imports the user's globally-
-    // installed pi-coding-agent which then needs to resolve
-    // `typebox` from its own node_modules. With --bytecode, that
-    // resolution falls back to the binary's snapshot and fails. The
-    // runtime startup cost of dropping --bytecode is small (~50-100ms);
-    // worth it for the resolver flexibility.
-    await $`bun build --compile --minify --target=${target} --define BUILD_VERSION='"${VERSION}"' src/index.ts --outfile ${outfilePath}`;
+    // --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');
+    const buildArgs = [
+      'build',
+      '--compile',
+      '--minify',
+      ...(useBytecode ? ['--bytecode'] : []),
+      `--target=${target}`,
+      '--define',
+      `BUILD_VERSION="${VERSION}"`,
+      'src/index.ts',
+      '--outfile',
+      outfilePath,
+    ];
+    await $`bun ${buildArgs}`;
     console.log(`  ✓ Built ${outfile}`);
   } catch (error) {
     console.error(`  ✗ Failed to build ${name}:`, error);

package/package.json

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

package/scripts/build-binaries.ts

@@ -525,17 +525,30 @@ for (const { name, target, outfile, ptyLib, ngrokLib, ngrokPkg } of selectedTarg
 
     // Build the binary (bun-pty and ngrok are now bundled via the generated loaders).
     //
-    // Note: deliberately NOT using --bytecode. Bytecode compilation
-    // freezes module resolution at build time, which breaks dynamic
-    // `import()` of absolute file:// URLs that have their own
-    // transitive deps (see oven-sh/bun#6893, #11732). The Pi SDK
-    // loader does exactly this — imports the user's globally-
-    // installed pi-coding-agent which then needs to resolve
-    // `typebox` from its own node_modules. With --bytecode, that
-    // resolution falls back to the binary's snapshot and fails. The
-    // runtime startup cost of dropping --bytecode is small (~50-100ms);
-    // worth it for the resolver flexibility.
-    await $`bun build --compile --minify --target=${target} --define BUILD_VERSION='"${VERSION}"' src/index.ts --outfile ${outfilePath}`;
+    // --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');
+    const buildArgs = [
+      'build',
+      '--compile',
+      '--minify',
+      ...(useBytecode ? ['--bytecode'] : []),
+      `--target=${target}`,
+      '--define',
+      `BUILD_VERSION="${VERSION}"`,
+      'src/index.ts',
+      '--outfile',
+      outfilePath,
+    ];
+    await $`bun ${buildArgs}`;
     console.log(`  ✓ Built ${outfile}`);
   } catch (error) {
     console.error(`  ✗ Failed to build ${name}:`, error);