A Node.js utility for running AppleScript code and returning the result. It provides an async `runAppleScript` (Promise of a string) and a synchronous `runAppleScriptSync` (string result), with options like `humanReadableOutput` to control output formatting and `signal` to cancel execution.
Project status
- The source appears quiet, with the last documented update on 2025-09-09 (about 9 months ago as of 2026-06-09), and no evidence in the provided history of ongoing rapid activity or new major work since then.
- Update cadence looks low-to-moderate overall, with major updates in 2021 (v5), 2022 (v6), 2023 (v7), and 2025 (v7.1), and longer gaps between earlier releases (for example, ~2 years from v4 to v5, then ~1 year from v6 to v7.0).
AI summary generated
Recent updates
v7.1.0
v7.1.0 adds cancellation support to the async `runAppleScript` API by introducing a new `signal` option (AbortSignal). The implementation forwards the signal to Node's `execFile` so the underlying `osascript` process can be aborted.
Featuresv7.0.0
v7.0.0 primarily updates the package to require Node.js 18. The diff also replaces the internal execution mechanism from execa to Node's child_process APIs and adjusts output handling and process options.
Breakingv6.1.0
v6.1.0 adds a new option, `humanReadableOutput`, to control how `osascript` formats results. The async and sync APIs were extended to accept an optional options object, and tests and documentation were updated accordingly.
Featuresv6.0.0
v6.0.0 primarily changes the public async API by renaming the exported function. The code diff also includes CI workflow updates and dependency version bumps, none of which are covered by the release notes.
Breakingv5.0.0
v5.0.0 converts the package to pure ESM, drops the default export, and introduces two named exports: runAppleScriptAsync and runAppleScriptSync. It also raises the minimum Node.js version to 12 and updates the project tooling and dependencies.
Breakingv4.0.0
v4.0.0 introduces TypeScript type definitions for the package and makes a major runtime requirement change. The release is labeled breaking because it requires an updated Node.js version to run the library.
BreakingFeatures