/
var
/
www
/
myprog.com.ua
/
server
/
node
/
node_modules
/
signal-exit
/
/var/www/myprog.com.ua/server/node/node_modules/signal-exit
mkdir
upload
Name
Size
Mode
Actions
index.js
5708
0644
edit
dl
rm
LICENSE.txt
748
0644
edit
dl
rm
package.json
864
0644
edit
dl
rm
README.md
1343
0644
edit
dl
rm
signals.js
1295
0644
edit
dl
rm
Edit:
/var/www/myprog.com.ua/server/node/node_modules/signal-exit/README.md
(1343B)
# signal-exit [](https://travis-ci.org/tapjs/signal-exit) [](https://coveralls.io/r/tapjs/signal-exit?branch=master) [](https://www.npmjs.com/package/signal-exit) [](https://github.com/conventional-changelog/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`. ```js 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.
Save
cmd:
run