Upgrading signal-exit from 3.x to 4.x
Comparison of the public API of signal-exit 3.0.7 and 4.1.0, computed automatically from their TypeScript types. A changed signature is a candidate for a breaking change, not a certainty.
Summary
| Removed import paths | 0 |
|---|---|
| Removed exports | 2 |
| Changed signatures | 3 |
| Removed class or interface members | 0 |
| Changed class or interface members | 0 |
| Newly deprecated | 0 |
| Requirement changes (engines, peer dependencies) | 1 |
| New exports | 2 |
Removed exports
| import | export | kind | Before |
|---|---|---|---|
signal-exit | Signal | type | string |
signal-exit | Options | interface | interface |
Changed signatures
| export | Before | After |
|---|---|---|
signal-exit · load | (): void | (): void |
signal-exit · unload | (): void | (): void |
signal-exit · signals | (): string[] | NodeJS.Signals[] |
Removed class or interface members
None detected.
Changed class or interface members
None detected.
Newly deprecated
None detected.
Requirement changes (engines, peer dependencies)
| Before | After | |
|---|---|---|
engines.node | — | >=14 |
New exports (2)
| import | export | kind |
|---|---|---|
signal-exit | onExit | variable |
signal-exit | Handler | type |
Frequently asked questions
What are the breaking changes when upgrading signal-exit from 3 to 4?
Between signal-exit 3.0.7 and 4.1.0, Vigia found 2 removed exports, 3 changed signatures and 0 removed or changed class or interface members.
What became deprecated in signal-exit 4?
0 exports or members are newly marked as deprecated in signal-exit 4.1.0.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/signal-exit/upgrade?from=3.0.7&to=4.1.0