@rayu-dev/rayu-cli 1.2.12 → 1.2.14

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rayu-dev/rayu-cli",
-  "version": "1.2.12",
+  "version": "1.2.14",
   "description": "Rayu-CLI — a multi-provider AI coding CLI",
   "type": "module",
   "bin": {
@@ -18,6 +18,7 @@
     "dev": "bun run src/entrypoints/cli.tsx",
     "build": "bun run scripts/build.ts",
     "build:binaries": "bun run scripts/build-binaries.ts",
+    "build-native": "bun run scripts/build-native.ts",
     "build:packages": "bun run scripts/build-packages.ts",
     "package": "bun run scripts/build-binaries.ts",
     "typecheck": "tsc --noEmit",
@@ -42,6 +43,7 @@
     "@aws-sdk/client-bedrock-runtime": "^3.1057.0",
     "@aws-sdk/client-sts": "^3.1057.0",
     "@commander-js/extra-typings": "12",
+    "@google/genai": "2.8.0",
     "@growthbook/growthbook": "^1.6.5",
     "@modelcontextprotocol/sdk": "^1.29.0",
     "@opentelemetry/api": "^1.9.1",

package/scripts/postinstall.cjs

@@ -33,16 +33,26 @@ function writeMarker() {
   } catch (_) {}
 }
 
-// npm v7+ pipes lifecycle script stdout/stderr, so we open /dev/tty directly
-// to write straight to the user's terminal (proven to work with PTY parent).
+// npm v7+ pipes lifecycle script stdout/stderr, so we open the terminal
+// device directly to write straight to the user's terminal.
+// On Unix: /dev/tty, on Windows: CON
+const isWindows = process.platform === 'win32';
+const ttyDevice = isWindows ? 'CON' : '/dev/tty';
+
 try {
-  const fd = fs.openSync('/dev/tty', 'w');
+  const fd = fs.openSync(ttyDevice, 'w');
   fs.writeSync(fd, message);
   fs.closeSync(fd);
   // Postinstall showed the message — mark as done so binary skips it
   writeMarker();
 } catch (_) {
-  // No controlling terminal (CI, Docker, Windows) — fall through.
-  // The binary will show the message on the user's first rayu run instead.
-  process.stdout.write(message);
+  // No controlling terminal (CI, Docker, headless) — fall through.
+  // Write to stdout as best-effort, and still write the marker so the
+  // binary doesn't try to show it again in a non-interactive context.
+  try {
+    process.stdout.write(message);
+  } catch (_e) {
+    // stdout may be closed in some CI environments
+  }
+  writeMarker();
 }