$ chmod +x vendor/snoreToast/snoretoast-*.exe

[mtsmfm]

Fixes #353.

Problem

In WSL2, node-notifier selects WindowsToaster (index.js:33-35), which spawns vendor/snoreToast/snoretoast-*.exe through Windows interop. Interop requires the executable bit on the Linux side, but the snoretoast binaries are shipped without it, so users see DEBUG=notifier output but no notification.

Evidence

The other shipped binaries (notifu, terminal-notifier) already have +x in the published tarball — only snoretoast is missing it:

$ npm pack node-notifier@10.0.1
$ tar -tvf node-notifier-10.0.1.tgz | grep -E "\.exe|terminal-notifier"
-rwxr-xr-x  package/vendor/mac.noindex/.../MacOS/terminal-notifier
-rwxr-xr-x  package/vendor/notifu/notifu.exe
-rwxr-xr-x  package/vendor/notifu/notifu64.exe
-rw-r--r--  package/vendor/snoreToast/snoretoast-x64.exe
-rw-r--r--  package/vendor/snoreToast/snoretoast-x86.exe

This traces back to the git blob mode — the snoretoast files were committed as 100644 (likely from a system that didn't preserve the executable bit during the upgrades in 8f01da4 / 54ddb7f), while notifu was added correctly as 100755:

$ git ls-tree HEAD vendor/snoreToast/ vendor/notifu/
100755 blob ... vendor/notifu/notifu.exe
100755 blob ... vendor/notifu/notifu64.exe
100644 blob ... vendor/snoreToast/snoretoast-x64.exe
100644 blob ... vendor/snoreToast/snoretoast-x86.exe

Fix

chmod +x the two files and commit, so the git blob mode flips to 100755 and the next publish picks it up.