Gathering detailed insights and metrics for @cjs-mifi-test/human-signals
Gathering detailed insights and metrics for @cjs-mifi-test/human-signals
Gathering detailed insights and metrics for @cjs-mifi-test/human-signals
Gathering detailed insights and metrics for @cjs-mifi-test/human-signals
npm install @cjs-mifi-test/human-signals
Typescript
Module System
Min. Node Version
Node Version
NPM Version
72.7
Supply Chain
99.3
Quality
75
Maintenance
100
Vulnerability
100
License
Total Downloads
1,992
Last Day
34
Last Week
361
Last Month
903
Last Year
1,115
Minified
Minified + Gzipped
Latest Version
3.0.1
Package Id
@cjs-mifi-test/human-signals@3.0.1
Unpacked Size
43.92 kB
Size
11.73 kB
File Count
12
NPM Version
8.1.0
Node Version
16.13.0
Cumulative downloads
Total Downloads
Last Day
36%
34
Compared to previous day
Last Week
33.7%
361
Compared to previous week
Last Month
3,373.1%
903
Compared to previous month
Last Year
147.2%
1,115
Compared to previous year
3
Human-friendly process signals.
This is a map of known process signals with some information about each signal.
Unlike
os.constants.signals
this includes:
1import { signalsByName, signalsByNumber } from 'human-signals' 2 3console.log(signalsByName.SIGINT) 4// { 5// name: 'SIGINT', 6// number: 2, 7// description: 'User interruption with CTRL-C', 8// supported: true, 9// action: 'terminate', 10// forced: false, 11// standard: 'ansi' 12// } 13 14console.log(signalsByNumber[8]) 15// { 16// name: 'SIGFPE', 17// number: 8, 18// description: 'Floating point arithmetic error', 19// supported: true, 20// action: 'core', 21// forced: false, 22// standard: 'ansi' 23// }
1npm install human-signals
This package is an ES module and must be loaded using
an import
or import()
statement,
not require()
.
Type: object
Object whose keys are signal names and values are signal objects.
Type: object
Object whose keys are signal numbers and values are signal objects.
Type: object
Signal object with the following properties.
Type: string
Standard name of the signal, for example 'SIGINT'
.
Type: number
Code number of the signal, for example 2
. While most number
are
cross-platform, some are different between different OS.
Type: string
Human-friendly description for the signal, for example
'User interruption with CTRL-C'
.
Type: boolean
Whether the current OS can handle this signal in Node.js using
process.on(name, handler)
.
The list of supported signals is OS-specific.
Type: string
Enum: 'terminate'
, 'core'
, 'ignore'
, 'pause'
, 'unpause'
What is the default action for this signal when it is not handled.
Type: boolean
Whether the signal's default action cannot be prevented. This is true
for
SIGTERM
, SIGKILL
and SIGSTOP
.
Type: string
Enum: 'ansi'
, 'posix'
, 'bsd'
, 'systemv'
, 'other'
Which standard defined that signal.
For any question, don't hesitate to submit an issue on GitHub.
Everyone is welcome regardless of personal background. We enforce a Code of conduct in order to promote a positive and inclusive environment.
This project was made with ❤️. The simplest way to give back is by starring and sharing it online.
If the documentation is unclear or has a typo, please click on the page's Edit
button (pencil icon) and suggest a correction.
If you would like to help us fix a bug or add a new feature, please check our guidelines. Pull requests are welcome!
Thanks go to our wonderful contributors:
ehmicky 💻 🎨 🤔 📖 | electrovir 💻 |
No vulnerabilities found.
No security vulnerabilities found.