@pylonsync/functions 0.3.259 → 0.3.261

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pylonsync/functions",
-  "version": "0.3.259",
+  "version": "0.3.261",
   "description": "TypeScript function runtime for pylon — defines server-side queries, mutations, and actions.",
   "type": "module",
   "main": "src/index.ts",

package/src/runtime.ts

@@ -942,12 +942,12 @@ async function main() {
       (f) => f.endsWith(".ts") || f.endsWith(".js")
     );
   } catch {
-    send({
-      type: "ready",
-      functions: [],
-      error: `Cannot read functions directory: ${fnDir}`,
-    });
-    return;
+    // No `functions/` directory. Legitimate for a pure-SSR app (file-based
+    // `app/**/page.tsx` routes + entity CRUD, no server functions) — the host
+    // still spawns this runner to execute SSR renders. Load zero functions and
+    // fall through so we send `ready` AND start the reader loop; returning here
+    // would leave the runner unable to serve renders (silent 404s).
+    files = [];
   }
 
   for (const file of files) {
@@ -989,7 +989,23 @@ async function main() {
   }));
   send({ type: "ready", functions });
 
+  // Belt-and-suspenders against orphaning: if the host dies in a way that
+  // somehow leaves our stdin open, we'll have been reparented to init
+  // (ppid === 1). Notice and exit. Unref'd so it never keeps us alive on its
+  // own.
+  const orphanWatch = setInterval(() => {
+    if (process.ppid === 1) process.exit(0);
+  }, 2000);
+  if (typeof orphanWatch.unref === "function") orphanWatch.unref();
+
   await readerLoop();
+
+  // readerLoop only returns when stdin hits EOF — i.e. the host (the pylon
+  // process that spawned us) is gone. Force-exit. We must NOT rely on the
+  // event loop draining on its own: the stdout writer, keep-alive sockets
+  // from `fetch`, and Bun's own handles keep the process alive, so every
+  // killed `pylon dev` would otherwise orphan its whole bun runner pool.
+  process.exit(0);
 }
 
 main().catch((err) => {