libreccm-legacy/trunk-images/node_modules/signal-exit
baka a212bb7b37 [3056] Adds Plugin to add Images from the system in tinymce. Now with files...
git-svn-id: https://svn.libreccm.org/ccm/trunk@5722 8810af33-2d31-482b-a856-94f89814c4df
2018-11-03 23:44:15 +00:00
..
CHANGELOG.md [3056] Adds Plugin to add Images from the system in tinymce. Now with files... 2018-11-03 23:44:15 +00:00
LICENSE.txt [3056] Adds Plugin to add Images from the system in tinymce. Now with files... 2018-11-03 23:44:15 +00:00
README.md [3056] Adds Plugin to add Images from the system in tinymce. Now with files... 2018-11-03 23:44:15 +00:00
index.js [3056] Adds Plugin to add Images from the system in tinymce. Now with files... 2018-11-03 23:44:15 +00:00
package.json [3056] Adds Plugin to add Images from the system in tinymce. Now with files... 2018-11-03 23:44:15 +00:00
signals.js [3056] Adds Plugin to add Images from the system in tinymce. Now with files... 2018-11-03 23:44:15 +00:00

README.md

signal-exit

Build Status Coverage NPM version Windows Tests 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.