Upgrading path-scurry from 1.x to 2.x
Comparison of the public API of path-scurry 1.11.1 and 2.0.2, 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 | 0 |
| Newly deprecated | 3 |
| Requirement changes (engines, peer dependencies) | 1 |
| New exports | 0 |
Removed exports
None detected.
Changed signatures
None detected.
Removed class or interface members
None detected.
Changed class or interface members
None detected.
Newly deprecated
| export | @deprecated |
|---|---|
path-scurry · PathBase.path | — |
path-scurry · PathPosix.path | — |
path-scurry · PathWin32.path | — |
Requirement changes (engines, peer dependencies)
| Before | After | |
|---|---|---|
engines.node | >=16 || 14 >=14.18 | 18 || 20 || >=22 |
Frequently asked questions
What are the breaking changes when upgrading path-scurry from 1 to 2?
Between path-scurry 1.11.1 and 2.0.2, Vigia found 0 removed exports, 0 changed signatures and 0 removed or changed class or interface members.
What became deprecated in path-scurry 2?
3 exports or members are newly marked as deprecated in path-scurry 2.0.2.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/path-scurry/upgrade?from=1.11.1&to=2.0.2