made-in-akira/node_modules/signal-exit
Akira Olivia Pink 83f1f9e08b added my css userstyles! and maybe some graphic design stuff? i've forgorten 2021-10-24 22:20:19 -03:00
..
LICENSE.txt added my css userstyles! and maybe some graphic design stuff? i've forgorten 2021-10-24 22:20:19 -03:00
README.md added my css userstyles! and maybe some graphic design stuff? i've forgorten 2021-10-24 22:20:19 -03:00
index.js added my css userstyles! and maybe some graphic design stuff? i've forgorten 2021-10-24 22:20:19 -03:00
package.json added my css userstyles! and maybe some graphic design stuff? i've forgorten 2021-10-24 22:20:19 -03:00
signals.js added my css userstyles! and maybe some graphic design stuff? i've forgorten 2021-10-24 22:20:19 -03:00

README.md

signal-exit

Build Status Coverage NPM version Standard Version

When you want to fire an event no matter how a process exits:

  • reaching the end of execution.
  • explicitly having process.exit(code) called.
  • having process.kill(pid, sig) called.
  • receiving a fatal signal from outside the process

Use signal-exit.

var onExit = require('signal-exit')

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

API

var remove = onExit(function (code, signal) {}, options)

The return value of the function is a function that will remove the handler.

Note that the function only fires for signals if the signal would cause the process to exit. That is, there are no other listeners, and it is a fatal signal.

Options

  • alwaysLast: Run this handler after any other signal or exit handlers. This causes process.emit to be monkeypatched.