@danypops/tickets 0.10.0 → 0.10.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@danypops/tickets",
-  "version": "0.10.0",
+  "version": "0.10.1",
   "description": "Unified CLI, daemon, and TypeScript library for issue tracking across GitHub, GitLab, and Jira.",
   "type": "module",
   "license": "MIT",

package/src/auth/browser.ts

@@ -9,8 +9,15 @@ import { spawn } from "node:child_process";
 
 export type Spawner = (command: string, args: string[]) => void;
 
-const defaultSpawner: Spawner = (command, args) => {
+// A spawn() failure (e.g. no `xdg-open` on a minimal Linux install) surfaces asynchronously as
+// an unlistened "error" event under Node, which is an uncaught exception that kills the whole
+// host process -- this runs from inside the long-lived pi-tickets extension host (tui.ts), not
+// just the standalone CLI, so that crash is a real live risk, not just a CLI inconvenience.
+export const defaultSpawner: Spawner = (command, args) => {
   const child = spawn(command, args, { stdio: "ignore", detached: true });
+  child.on("error", (error) => {
+    console.error(`failed to open URL via ${command}: ${error instanceof Error ? error.message : String(error)}`);
+  });
   child.unref();
 };
 

package/src/cli/tickets-client.ts

@@ -29,14 +29,22 @@ async function isAlive(handle: DaemonHandle, token: string): Promise<boolean> {
   }
 }
 
-/** Absolute path to the daemon's real entry point, resolved from this package's own root. Used both to spawn it on demand and to point a systemd unit's ExecStart at it (see cli/systemd-service.ts). */
+/** Absolute path to the daemon's real entry point, resolved from this package's own root. Used to spawn it on demand -- Armada's own ServiceSpec (see cli/systemd-service.ts) launches the CLI's own `serve` command instead, not this path directly. */
 export function resolveDaemonEntryPath(): string {
   const root = packageRoot(dirname(fileURLToPath(import.meta.url)));
   return join(root, "src", "process", "main.ts");
 }
 
-function spawnDaemon(): void {
+// A spawn() failure surfaces asynchronously as an unlistened "error" event under Node, which is
+// an uncaught exception that kills the whole host process. createTicketsClient (which calls
+// this via ensureDaemonRunning) runs from inside the long-lived pi-tickets extension host
+// (tui.ts) as well as the CLI, so a missing/misconfigured `bun` binary would otherwise crash
+// the whole Pi session, not just this one connect attempt.
+export function spawnDaemon(): void {
   const child = spawn("bun", ["run", resolveDaemonEntryPath()], { detached: true, stdio: "ignore" });
+  child.on("error", (error) => {
+    console.error(`tickets daemon auto-spawn failed: ${error instanceof Error ? error.message : String(error)}`);
+  });
   child.unref();
 }