Bernt
58ca4e68db
- Go backend API with full CRUD for all modules (CRM, Sales, Finance, HR, Legal, Marketing, Support, Purchase, Inventory, Projects, Automation, Analytics) - Rust analytics service with parallel report generation - C runtime with POSIX shared memory IPC - PostgreSQL schema with 30+ tables, full migrations - Redis cache, sessions, pub/sub - Kafka event streaming with Zookeeper - WebSocket hub for real-time updates - Automation engine with cron jobs, workflows, event triggers - JWT authentication, multi-tenant from start - Docker Compose with all services - Nginx reverse proxy with rate limiting - Integration tests passing - Feature gap analysis against Fortnox/Odoo/Visma Refs: BOC-001
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.
|