Upgrading path-key from 3.x to 4.x
Comparison of the public API of path-key 3.1.1 and 4.0.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 | 0 |
| Changed signatures | 0 |
| Removed class or interface members | 0 |
| Changed class or interface members | 1 |
| Newly deprecated | 0 |
| Requirement changes (engines, peer dependencies) | 1 |
| New exports | 1 |
Removed exports
None detected.
Changed signatures
None detected.
Removed class or interface members
None detected.
Changed class or interface members
| member | Before | After |
|---|---|---|
Options.env | { [key: string]: string | undefined; } | undefined | Record<string, string | undefined> | undefined |
Newly deprecated
None detected.
Requirement changes (engines, peer dependencies)
| Before | After | |
|---|---|---|
engines.node | >=8 | >=12 |
New exports (1)
| import | export | kind |
|---|---|---|
path-key | default | function |
Frequently asked questions
What are the breaking changes when upgrading path-key from 3 to 4?
Between path-key 3.1.1 and 4.0.0, Vigia found 0 removed exports, 0 changed signatures and 1 removed or changed class or interface members.
What became deprecated in path-key 4?
0 exports or members are newly marked as deprecated in path-key 4.0.0.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/path-key/upgrade?from=3.1.1&to=4.0.0