Upgrading foreground-child from 3.x to 4.x
Comparison of the public API of foreground-child 3.3.1 and 4.0.3, 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 | 0 |
| Changed signatures | 1 |
| Removed class or interface members | 0 |
| Changed class or interface members | 0 |
| Newly deprecated | 0 |
| Requirement changes (engines, peer dependencies) | 1 |
| New exports | 0 |
Removed exports
None detected.
Changed signatures
| export | Before | After |
|---|---|---|
foreground-child/watchdog · watchdog | (child: ChildProcess): ChildProcess | (child: ChildProcess): any |
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 | >=16 |
Frequently asked questions
What are the breaking changes when upgrading foreground-child from 3 to 4?
Between foreground-child 3.3.1 and 4.0.3, Vigia found 0 removed exports, 1 changed signatures and 0 removed or changed class or interface members.
What became deprecated in foreground-child 4?
0 exports or members are newly marked as deprecated in foreground-child 4.0.3.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/foreground-child/upgrade?from=3.3.1&to=4.0.3