Human-friendly process signals
APACHE-2.0 License
SignalNumber
and Signal['number']
types in TypeScript are now stricter. They only allow valid signal numbers like 1 or 9. They do not allow invalid signal numbers like -1, 1.5 or 999. Please note that 0 is not considered a valid signal number, although it can be passed to process.kill()
.signalsByName[signalName]
and signalsByNumber[signalNumber]
types in TypeScript are now Signal
instead of Signal | undefined
. This means you can now do signalsByName[signalName].description
instead of signalsByName[signalName]!.description
.Published by ehmicky 6 months ago
SignalName
and Signal['name']
types in TypeScript are now stricter. They only allow valid signal names like 'SIGINT'
. They do not allow lowercase signals like 'sigint'
nor unknown signals like 'SIGOTHER'
.Published by ehmicky 12 months ago
18.18.0
Published by ehmicky over 1 year ago
16.17.0
Published by ehmicky over 1 year ago
Published by ehmicky almost 2 years ago
Published by ehmicky about 2 years ago
Published by ehmicky over 2 years ago
Published by ehmicky over 2 years ago
14.18.0
Published by ehmicky over 3 years ago
main
field in package.json
Published by ehmicky over 3 years ago
12.20.0
import
or import()
statement, not require()
. See this post for more information.Published by ehmicky over 4 years ago
Published by ehmicky almost 5 years ago
10.17.0
Published by ehmicky about 5 years ago
core-js
dependency (33330d2)Published by ehmicky about 5 years ago
Related
section (1d555a7)Published by ehmicky about 5 years ago
source
to standard
(70d46af)Published by ehmicky about 5 years ago