Skip to content

A Node.js module for sending notifications on native Mac, Windows and Linux (or Growl as fallback)

active 2023-08-172026-07-27 (UTC)

Complete coverage26,509 / 26,509 hourly files (100%) · 2 absent upstream2023-08-152026-08-23 (UTC)
Events
337
Pushes
0
Pull requests
4
Issues
26
Stars
243
Forks
26

Activity over time

Daily event counts in the loaded window

Line chart, 1076 days from 2023-08-17 to 2026-07-27. Pushes: 0 total, peak 0 in a day. Pull requests: 4 total, peak 2 in a day. Issues: 26 total, peak 4 in a day. Comments: 38 total, peak 4 in a day. Stars: 243 total, peak 4 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

Recent activity

Latest issues, pull requests and releases

  • Issue comment#455SpencerKaiser2026-03-03 22:36
    fileCommandJson sometimes receives JSON lines that it can't parse.
  • Issue#457beautyfree2026-02-01 01:36
    Add ability to use package by `npx`
  • Issue#455strongpauly2025-06-27 09:04
    fileCommandJson sometimes receives JSON lines that it can't parse.
  • Issue comment#441Sebastian-Webster2025-05-15 11:49
    feat: Allow node-notifier to work on Apple Silicon Macs
  • Issue comment#441mikaelbr2025-05-15 09:53
    feat: Allow node-notifier to work on Apple Silicon Macs
  • Issue comment#441DerZyklop2025-05-15 09:44
    feat: Allow node-notifier to work on Apple Silicon Macs
  • Issue comment#401leep-frog2025-03-14 03:11
    timeout option doesn't work
  • Issue comment#413WORMSS2025-02-19 14:56
    Uncaught (in promise) TypeError: options.message.replace is not a function
  • Issue comment#454steve020815042025-01-30 02:59
    Uncaught (in promise) Error: Not implemented: Pipe.prototype.listen - Windows
  • Issue#454steve020815042025-01-30 02:59
    Uncaught (in promise) Error: Not implemented: Pipe.prototype.listen - Windows
  • Issue comment#454steve020815042025-01-29 08:08
    Uncaught (in promise) Error: Not implemented: Pipe.prototype.listen - Windows
  • Issue#454steve020815042025-01-29 01:20
    Uncaught (in promise) Error: Not implemented: Pipe.prototype.listen - Windows
  • Issue comment#440NullClock2024-10-31 03:54
    [SUGGESTION] ..
  • Issue comment#440mikaelbr2024-10-30 21:29
    [SUGGESTION] ..
  • Issue#440mikaelbr2024-10-30 21:29
    [SUGGESTION] ..
  • Issue comment#448mikaelbr2024-10-30 21:27
    Minor log pollution on Win11 when using actions
  • Issue#448mikaelbr2024-10-30 21:27
    Minor log pollution on Win11 when using actions
  • Issue comment#449mikaelbr2024-10-30 21:26
    An unexpected error occurred: "https://registry.yarnpkg.com/node-notifier/-/node-notifier-5.4.5.tgz: Request failed \"503 Service Unavailable\""
  • Issue#449mikaelbr2024-10-30 21:26
    An unexpected error occurred: "https://registry.yarnpkg.com/node-notifier/-/node-notifier-5.4.5.tgz: Request failed \"503 Service Unavailable\""
  • Issue comment#443mikaelbr2024-10-30 21:25
    503 Service Unavailable - node-notifier-5.4.5.tgz
  • Issue#443mikaelbr2024-10-30 21:25
    503 Service Unavailable - node-notifier-5.4.5.tgz
  • Issue#452mikaelbr2024-10-24 08:38
    We just switched to the new Proto library build rules in the [instrumentation-proto](https://github.com/google/instrumentation-proto) repository, by following the instructions at https://bazel.build/blog/index.html#protocol-buffers-in-bazel. Here is the pull request: https://github.com/google/instrumentation-proto/pull/26
  • Issue#453mikaelbr2024-10-24 08:38
    OK sorry for the false positive, I didn't know about the single `&` operator and thought that was the thing which was breaking my build (it went a bit further at the time when using `&&`, but now I notice this is not the issue indeed).
  • Issue#451mikaelbr2024-10-24 08:38
    gh pr checkout 432
  • Issue comment#453oleole392024-10-19 13:04
    OK sorry for the false positive, I didn't know about the single `&` operator and thought that was the thing which was breaking my build (it went a bit further at the time when using `&&`, but now I notice this is not the issue indeed).

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 243 stars here means stars gained during the window, not the repo's star count.