</>PackageGraphPackageGraph

signal-exit

npmv4.1.0TypeScript

when you want to fire an event no matter how a process exits.

Not recommended for new projects

No — signal-exit should not be adopted for new projects. Last published 1139 days ago.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • FMaintenance: grade F, Failing.

    Last published 1139 days ago.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 75 KB installed.

  • ASupply chain: grade A, Excellent.

    No install scripts, 2 maintainers, and a contained dependency surface.

  • ALicense: grade A, Excellent.

    ISC — permissive, with no copyleft found in the dependency tree.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding signal-exit to a project.

0
Direct dependencies

Runtime packages this one declares itself.

0
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

75 KB
Install size

Unpacked size of this package plus its entire runtime tree.

—
Tree depth

Longest resolved dependency chain below this package.

Compatibility

Node.js
node >=14
Module format
ESM + CommonJS
TypeScript
Types included
Install scripts
None

Quick start

A usage example from the signal-exit README.

jsFull README ↗
// Hybrid module, either works
import { onExit } from 'signal-exit'
// or:
// const { onExit } = require('signal-exit')

onExit((code, signal) => {
  console.log('process exited!', code, signal)
})

signal-exit vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
signal-exitthis page02ISC3 years ago
exit-x04MIT1 day ago
abort-controller04MIT1 day ago

Dependencies

Declared by signal-exit v4.1.0. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (10)

@types/cross-spawn ^6.0.2@types/node ^18.15.11@types/signal-exit ^3.0.1@types/tap ^15.0.8c8 ^7.13.0prettier ^2.8.6tap ^16.3.4ts-node ^10.9.1typedoc ^0.23.28typescript ^5.0.2

Used by

Popular packages that depend on signal-exit.

rolldownnpm

Fast JavaScript/TypeScript bundler in Rust with Rollup-compatible API.

↓ 81.9M/wk◈ 8 dependents⚖ MITTS
write-file-atomicnpm

Write files in an atomic fashion w/configurable ownership

↓ 0/wk◈ 2 dependents⚖ ISC

Relationship graph

Dependencies (left) and dependents (right) of signal-exit.

rolldownwrite-file-atomicsignal-exit
signal-exit dependencies dependents

Frequently installed together

@rolldown/pluginutilsnpm

Plugin utilities for Rolldown

↓ 132.4M/wk◈ 1 dependents⚖ MIT
rolldownnpm

Fast JavaScript/TypeScript bundler in Rust with Rollup-compatible API.

↓ 81.9M/wk◈ 8 dependents⚖ MITTS
cacnpm

Simple yet powerful framework for building command-line apps.

↓ 44M/wk◈ 9 dependents⚖ MIT
valibotnpm

The modular and type safe schema library for validating structural data

↓ 16.8M/wk◈ 5 dependents⚖ MITTS
pathenpm

Universal filesystem path utils

↓ 0/wk◈ 25 dependents⚖ MITTS
globnpm

the most correct and second fastest glob implementation in JavaScript

↓ 0/wk◈ 35 dependents⚖ BlueOak-1.0.0TS
source-mapnpm

Generates and consumes source maps

↓ 0/wk◈ 16 dependents⚖ BSD-3-ClauseTS

Release history

No releases in the last two years, typically about 25 days apart.

Recent versions of signal-exit
VersionPublishedSizeLicense
4.1.0latest3 years ago75 KBISC
4.0.33 years ago72 KBISC
4.0.23 years ago70 KBISC
4.0.13 years ago71 KBISC
4.0.03 years ago68 KBISC
3.0.74 years ago9.7 KBISC
3.0.64 years ago9.7 KBISC
3.0.55 years ago9.0 KBISC
3.0.45 years ago9.0 KBISC
3.0.36 years ago9.6 KBISC
3.0.29 years ago—ISC
3.0.110 years ago—ISC
3.0.010 years ago—ISC
3.0.0-candidate10 years ago—ISC
2.1.211 years ago—ISC

Overview

signal-exit is an npm package that when you want to fire an event no matter how a process exits. It has 2 known dependents in the graph. The latest version is 4.1.0, released under the ISC license.

Who should use it

Teams working in the npm ecosystem who need when you want to fire an event no matter how a process exits and value a focused solution.

When not to use it

Consider an alternative if you need to or if a more actively-maintained option better fits your npm stack.

Pros

  • Ships TypeScript type definitions.
  • Clear open-source license (ISC).

Cons

  • No significant drawbacks detected from available metadata.

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

bcoeisaacs

Keywords

exitsignal

Funding

Frequently asked questions

Should I use signal-exit?

No — signal-exit should not be adopted for new projects. Last published 1139 days ago.

How do I install signal-exit?

Run `npm install signal-exit` to add signal-exit to your npm project.

What license is signal-exit released under?

signal-exit is distributed under the ISC license.

How popular is signal-exit?

npm does not publish download counts. Within PackageGraph's crawl, 2 known packages depend on signal-exit.

Is signal-exit still maintained?

The most recent release of signal-exit (v4.1.0) was published 3 years ago.

Does signal-exit run install scripts?

No. signal-exit does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.