fix(timer): stop crashing when the timer expires on Apple Silicon

[aversini]

What was broken

Every timer crashed the moment it expired:

❯ t 2s
┌ Timer Configuration ┐
│     0h 0m 2s        │
└─────────────────────┘

Error: spawn Unknown system error -86
    at ChildProcess.spawn (node:internal/child_process:441:11)
    at module.exports.fileCommandJson (node-notifier/lib/utils.js:88:13)
    at NotificationCenter.notifyRaw (node-notifier/notifiers/notificationcenter.js:81:11)
    at Timeout._onTimeout (@node-cli/timer/dist/utilities.js:65:30)

Notifications default to on, so this made the tool unusable on affected machines.

Root cause

On Darwin, errno 86 is EBADARCH — "Bad CPU type in executable".

node-notifier displays macOS notifications by spawning a vendored binary at vendor/mac.noindex/terminal-notifier.app. That binary is x86_64-only:

$ lipo -archs .../terminal-notifier
x86_64

On an Apple Silicon host with Rosetta 2 not installed, it cannot run at all:

$ .../terminal-notifier -help
bad CPU type in executable

execFile throws that EBADARCH synchronously, straight up through the unguarded notifier.notify() call inside the setTimeout expiry callback, where nothing caught it. A cosmetic failure became an uncaught exception that killed the process.

The fix

Notifications now use the notifier each OS already ships, so nothing is vendored and nothing is coupled to a CPU architecture:

Platform	Notifier
macOS	osascript (arm64e, always present)
Linux	notify-send
Windows	PowerShell WinRT toast

notify() resolves to false on any failure — unsupported platform, missing notifier, notifier that refuses to run — instead of throwing. A notification can no longer take the timer down.

node-notifier is dropped entirely: it is unmaintained (10.0.1 is its final release), and this removes ~4MB of unrunnable vendored binaries plus 47 lockfile lines.

Verification

End-to-end, the exact failing command:

$ node dist/timer.js 2s
✔ Time's up!
EXIT_CODE=0

The notification is confirmed delivered rather than silently swallowed (notify delivered: true).

Full suite green across all 12 projects; timer at 13/13.

The regression tests are meaningful — with the guard removed, both failure tests fail (promise rejected ... instead of resolving); restored, they pass. notify.test.ts reproduces the exact EBADARCH synchronous throw (errno -86, syscall spawn), plus ENOENT, unsupported-platform, and command-construction/escaping cases.

Consumer impact

• node-notifier is no longer a dependency.
• wait: true is gone. The process no longer stays alive until the notification is dismissed; it exits once the notification is delivered.

Not included

Left for separate PRs, as they are unrelated to this crash:

• 3 pre-existing lint warnings in utilities.test.ts (unused path/Duration/vi imports), identical before and after this change.
• @types/node-notifier still arrives transitively via @versini/dev-dependencies-common — types-only and harmless, but removing it means touching another repo.

🤖 Generated with Claude Code

https://claude.ai/code/session_01PmVBQszqooNXgLX5x6VTth

[Copilot]

Copilot reviewed 4 out of 5 changed files in this pull request and generated no comments.

Files not reviewed (1)

• pnpm-lock.yaml: Generated file