Linux premium71.web-hosting.com 4.18.0-513.11.1.lve.el8.x86_64 #1 SMP Thu Jan 18 16:21:02 UTC 2024 x86_64
LiteSpeed
Server IP : 198.187.29.8 & Your IP : 18.191.158.217
Domains :
Cant Read [ /etc/named.conf ]
User : cleahvkv
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
lib /
node_modules /
npm /
node_modules /
signal-exit /
Delete
Unzip
Name
Size
Permission
Date
Action
CHANGELOG.md
1.05
KB
-rw-r--r--
2021-03-10 14:36
LICENSE.txt
748
B
-rw-r--r--
2021-03-10 14:36
README.md
1.46
KB
-rw-r--r--
2021-03-10 14:36
index.js
3.82
KB
-rw-r--r--
2021-03-10 14:36
package.json
1.78
KB
-rw-r--r--
2021-03-10 14:36
signals.js
1.26
KB
-rw-r--r--
2021-03-10 14:36
Save
Rename
# 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://ci.appveyor.com/project/bcoe/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 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.