runAppleScript: report effective timeout in errors

docs/utils-reference/getting-started.md

@@ -16,6 +16,10 @@ npm install --save @raycast/utils
 
 ## Changelog
 
+### v2.2.7
+
+- Fixed `runAppleScript` timeout error messages reporting `undefined` instead of the effective timeout.
+
 ### v2.2.6
 
 - Fixed an issue where refreshing OAuth tokens would fails for providers that return scope as an array instead of a string

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@raycast/utils",
-  "version": "2.2.6",
+  "version": "2.2.7",
   "description": "Set of utilities to streamline building Raycast extensions",
   "author": "Raycast Technologies Ltd.",
   "homepage": "https://developers.raycast.com/utilities/getting-started",

src/run-applescript.ts

@@ -103,7 +103,8 @@ export async function runAppleScript<T = string>(
     ...execOptions,
     env: { PATH: "/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin" },
   });
-  const spawnedPromise = getSpawnedPromise(spawned, { timeout: timeout ?? 10000 });
+  const effectiveTimeout = timeout ?? 10000;
+  const spawnedPromise = getSpawnedPromise(spawned, { timeout: effectiveTimeout });
 
   spawned.stdin.end(script);
 
@@ -123,7 +124,12 @@ export async function runAppleScript<T = string>(
     signal,
     timedOut,
     command: "osascript",
-    options,
+    options: {
+      humanReadableOutput,
+      language,
+      timeout: effectiveTimeout,
+      ...execOptions,
+    },
     parentError: new Error(),
   });
 }