A Node.js package that provides a human-friendly map of known process signals, including readable descriptions, default actions, whether they are supported on the current OS, and whether the default action can be prevented. It’s useful for writing clearer signal and error-handling logic around interrupts and process exit behavior.
Project status
- Actively maintained: The upstream repo shows a very recent push on 2025-05-25, and a tagged update 8.0.1 exists on 2025-03-29, indicating continued activity rather than abandonment.
- Update cadence (evident from tags): Updates appear irregular but fairly steady, with v7.0.0 on 2024-05-04, v8.0.0 on 2024-08-03 (about 3 months later), and v8.0.1 on 2025-03-29 (about 7-8 months later).
AI summary generated Today
Recent updates
8.0.1
3/29/2025Release v8.0.1 is primarily a documentation update (README and related contributor-facing docs). The code diff also includes non-runtime tooling and dependency changes, including a shift in ESLint and Prettier configuration files and updated devDependencies with corresponding lockfile churn.
8.0.0
8/3/2024Release v8.0.0 tightens the TypeScript typing around POSIX signal numbers and signal lookup tables. The biggest change is that `SignalNumber` becomes an explicit union of allowed numeric literals, and `signalsByName` and `signalsByNumber` are typed as always returning a `Signal` (no more `undefined`).
Breaking7.0.0
5/4/2024Release v7.0.0 tightens the TypeScript signal name typings to only allow known POSIX-style signal identifiers like 'SIGINT'. The main documented change is the stricter SignalName and Signal['name'] types.
Breaking6.0.0
10/28/2023Release v6.0.0 updates the project to require Node.js >= 18.18.0. Aside from that stated breaking change, the diff mostly affects documentation, metadata, and development tooling dependencies and lockfiles.
Breaking5.0.0
5/13/2023v5.0.0 primarily updates the project requirements to use Node.js >= 16.17.0. The diff also shows broad dependency lockfile churn and changes to development tooling versions, plus a README update reflecting the new Node minimum.
Breaking4.3.1
3/19/2023Release v4.3.1 is described as a small bug fix for removing a source map comment from the built package. The actual diff includes multiple build and TypeScript definition publishing changes, plus dependency bumps that are not mentioned in the release notes.
4.3.0
11/11/2022Release 4.3.0 claims to improve tree-shaking support. The code diff shows the tree-shaking work was implemented mainly via package.json packaging changes (exports, sideEffects, files) plus a set of Node.js import-specifier cleanups.
Features4.2.0
8/16/2022Release 4.2.0 primarily claims a package size reduction. The code diff shows that the npm package contents were substantially trimmed via the package.json files whitelist, and build/type-checking configuration was also adjusted.
Features4.1.0
6/26/2022Release 4.1.0 is described as a TypeScript typing improvement. The diff shows substantial tightening and restructuring of the public .d.ts types, including template-literal typing for signal names and more restrictive index signatures for the exported signal lookup objects.
Features4.0.0
5/9/2022Release 4.0.0 primarily updates the package to require Node.js 14.18.0+. The code diff also shows internal refactors to how exports are constructed, plus multiple repository and CI tooling updates.
Breaking