@isomorph.ai/app-sdk 1.13.0 → 1.13.1

package/dist/runtime.js

@@ -54,6 +54,7 @@ import { createServer } from 'node:http';
 import { readFile, readdir, stat } from 'node:fs/promises';
 import { register } from 'node:module';
 import { join, resolve } from 'node:path';
+import { realpathSync } from 'node:fs';
 import { pathToFileURL } from 'node:url';
 import { createClient, IsomorphError } from './index.js';
 import { userGroupsFromHeader } from './user-groups.js';
@@ -629,7 +630,19 @@ export function runJobFromArguments(argv = process.argv.slice(2)) {
     }
     return undefined;
 }
-const entry = process.argv[1] ? pathToFileURL(process.argv[1]).href : '';
+// Node resolves this module's URL through any symlink in its path, while
+// process.argv[1] is the path the starter typed. On macOS /tmp and /var are
+// symlinks, so a gate or `isomorph dev` started from an app root under them
+// handed a path whose URL never matched, and the runtime loaded as a library
+// and exited 0 without a word (the gate reported "exited before it
+// answered", 2026-10-06). Compare the real path, as Node did.
+const entryPath = process.argv[1] ? (() => { try {
+    return realpathSync(process.argv[1]);
+}
+catch {
+    return process.argv[1];
+} })() : '';
+const entry = entryPath ? pathToFileURL(entryPath).href : '';
 if (import.meta.url === entry) {
     // Extensionless relative imports in the app's server code resolve to
     // their .ts files (runtime-hooks.ts); registered before any app module

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@isomorph.ai/app-sdk",
-  "version": "1.13.0",
+  "version": "1.13.1",
   "type": "module",
   "repository": {
     "type": "git",