start-command 0.17.1 → 0.17.2

package/CHANGELOG.md

@@ -1,5 +1,16 @@
 # start-command
 
+## 0.17.2
+
+### Patch Changes
+
+- d38a67f: fix: Use 'close' event instead of 'exit' for reliable stdout capture on macOS
+
+  The 'exit' event fires when the process terminates, but stdio streams may still have buffered data. On macOS, fast-executing commands like 'echo hi' could exit before stdout data events fired, causing no output to be displayed and no finish block shown.
+  - Changed from 'exit' to 'close' event in JavaScript for reliable output capture
+  - Updated Rust to use piped stdout/stderr with threads for real-time display and capture
+  - Added case study documentation for Issue #57 root cause analysis
+
 ## 0.17.1
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "start-command",
-  "version": "0.17.1",
+  "version": "0.17.2",
   "description": "Gamification of coding, execute any command with ability to auto-report issues on GitHub",
   "main": "src/bin/cli.js",
   "exports": {

package/src/bin/cli.js

@@ -640,8 +640,11 @@ function runDirect(cmd, sessionId) {
     logContent += text;
   });
 
-  // Handle process exit
-  child.on('exit', (code) => {
+  // Handle process close (not 'exit' - we need to wait for all stdio to be closed)
+  // The 'close' event fires after all stdio streams have been closed, ensuring
+  // all stdout/stderr data has been received. The 'exit' event can fire before
+  // buffered data is received, causing output loss on macOS (Issue #57).
+  child.on('close', (code) => {
     const exitCode = code || 0;
     const endTime = getTimestamp();