History

Florian Dold 82f2b76e25 Reorganize module loading. We now use webpack instead of SystemJS, effectively bundling modules into one file (plus commons chunks) for every entry point. This results in a much smaller extension size (almost half). Furthermore we use yarn/npm even for extension run-time dependencies. This relieves us from manually vendoring and building dependencies. It's also easier to understand for new developers familiar with node.		2017-04-24 16:14:29 +02:00
..
CHANGELOG.md	add node_modules to address #4364	2016-10-10 03:43:44 +02:00
index.js	Reorganize module loading.	2017-04-24 16:14:29 +02:00
LICENSE.txt	add node_modules to address #4364	2016-10-10 03:43:44 +02:00
package.json	Reorganize module loading.	2017-04-24 16:14:29 +02:00
README.md	add node_modules to address #4364	2016-10-10 03:43:44 +02:00
signals.js	add node_modules to address #4364	2016-10-10 03:43:44 +02:00

README.md

signal-exit

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.