Upgrading pathe from 1.x to 2.x
Comparison of the public API of pathe 1.1.2 and 2.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 | 3 |
| Removed class or interface members | 0 |
| Changed class or interface members | 0 |
| Newly deprecated | 0 |
| Requirement changes (engines, peer dependencies) | 0 |
| New exports | 4 |
Removed exports
None detected.
Changed signatures
| export | Before | After |
|---|---|---|
pathe · default | namespace | any |
pathe · delimiter | ":" | ";" | ":" |
pathe/utils · filename | (path: string): string | (path: string): string | undefined |
Removed class or interface members
None detected.
Changed class or interface members
None detected.
Newly deprecated
None detected.
Requirement changes (engines, peer dependencies)
None detected.
New exports (4)
| import | export | kind |
|---|---|---|
pathe | posix | variable |
pathe | win32 | variable |
pathe | matchesGlob | variable |
pathe/utils | reverseResolveAlias | function |
Frequently asked questions
What are the breaking changes when upgrading pathe from 1 to 2?
Between pathe 1.1.2 and 2.0.3, Vigia found 0 removed exports, 3 changed signatures and 0 removed or changed class or interface members.
What became deprecated in pathe 2?
0 exports or members are newly marked as deprecated in pathe 2.0.3.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/pathe/upgrade?from=1.1.2&to=2.0.3