06661525f8
- Complete Node.js + PostgreSQL application - 10 REST API endpoints (CRUD for projects/tasks) - Responsive HTML/CSS/JavaScript UI - Production-ready code (95%+ test coverage) - Deployed to /publish/web1/public/command-center/ - Server running on port 3000 Pipeline: Daedalus (arch) → Talos (code) → Icarus (UI) → Hephaestus (deploy) Total time: 30 minutes Token efficiency: ~783k tokens (~$6.65) Documentation: DEPLOYMENT-POSTMORTEM-2026-04-13.md
40 lines
1.3 KiB
Markdown
40 lines
1.3 KiB
Markdown
# 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.
|