Skip to content

Releases: ehmicky/human-signals

v8.0.0

03 Aug 19:58
Compare
Choose a tag to compare

Breaking changes (types)

  • The 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().

Types

  • The 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.

v7.0.0

04 May 02:31
Compare
Choose a tag to compare

Breaking changes (types)

  • The 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'.

v6.0.0

28 Oct 22:19
Compare
Choose a tag to compare

Breaking changes

  • Minimal supported Node.js version is now 18.18.0

v5.0.0

13 May 23:49
Compare
Choose a tag to compare

Breaking changes

  • Minimal supported Node.js version is now 16.17.0

v4.3.1

19 Mar 02:20
Compare
Choose a tag to compare

Bug fixes

  • Remove source map comment from built package (#15)

Release 4.3.0

11 Nov 18:59
Compare
Choose a tag to compare

Features

  • Improve tree-shaking support

Release 4.2.0

16 Aug 19:17
Compare
Choose a tag to compare

Features

  • Reduce npm package size

Release 4.1.0

26 Jun 19:30
Compare
Choose a tag to compare

Features

  • Improve TypeScript types

Release 4.0.0

09 May 20:28
Compare
Choose a tag to compare

Breaking changes

  • Minimal supported Node.js version is now 14.18.0

Release 3.0.1

22 Jun 12:22
Compare
Choose a tag to compare

Bug fixes

  • Fix main field in package.json