Repositorio del curso CCOM4030 el semestre B91 del proyecto Artesanías con el Instituto de Cultura
lyxaira.glass 74ca844f42 Actualizacion cambios generados: seccion #12, #14 y #15. 4 anni fa
..
CHANGELOG.md Actualizacion cambios generados: seccion #12, #14 y #15. 4 anni fa
LICENSE.txt Actualizacion cambios generados: seccion #12, #14 y #15. 4 anni fa
README.md Actualizacion cambios generados: seccion #12, #14 y #15. 4 anni fa
index.js Actualizacion cambios generados: seccion #12, #14 y #15. 4 anni fa
package.json Actualizacion cambios generados: seccion #12, #14 y #15. 4 anni fa
signals.js Actualizacion cambios generados: seccion #12, #14 y #15. 4 anni fa

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 proces 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.