Tenative fix for #16

A theory from claude is that since we were fire-and-forget-ing `main`,
the node process can die before flushing the full contents to stdout,
leaving `less` in a different mode because of control characters.

I'm not completely convinced because I/O should keep the process alive,
but maybe there's still a race condition possible and this change seems
harmless.

Author: banga

src/index.ts

@@ -19,6 +19,22 @@ async function main() {
         terminalSize().columns
     );
     await transformContentsStreaming(context, process.stdin, process.stdout);
+
+    // Ensure stdout is fully flushed before exiting
+    // This is critical when piping to `less` - if we exit before stdout is drained,
+    // less may not receive all data or may receive it in a broken state
+    if (process.stdout.writableNeedDrain) {
+        await new Promise<void>((resolve) => {
+            process.stdout.once('drain', resolve);
+        });
+    }
 }
 
-main();
+main().catch((err) => {
+    // Don't print errors if stdout pipe was closed (EPIPE)
+    // This happens when less quits before we finish processing
+    if (err.code !== 'EPIPE') {
+        console.error(err);
+        process.exit(1);
+    }
+});

src/transformContentsStreaming.ts

@@ -30,7 +30,8 @@ export function transformContentsStreaming(
                     case 'EPIPE':
                         // This can happen if the process exits while we are still
                         // processing the input and writing to stdout.
-                        break;
+                        resolve();
+                        return;
                     default:
                         reject(err);
                         return;