Vigia

Upgrading locate-path from 7.x to 8.x

Comparison of the public API of locate-path 7.2.0 and 8.0.0, computed automatically from their TypeScript types. A changed signature is a candidate for a breaking change, not a certainty.

Summary

Removed import paths0
Removed exports0
Changed signatures2
Removed class or interface members0
Changed class or interface members0
Newly deprecated0
Requirement changes (engines, peer dependencies)1
New exports0

Removed exports

None detected.

Changed signatures

exportBeforeAfter
locate-path · Optionsinterface{ readonly cwd?: string | URL | undefined; readonly type?: "file" | "directory" | "both" | undefined; readonly allowSymlinks?: boolean | undefined; }
locate-path · AsyncOptionsinterface{ readonly concurrency?: number | undefined; readonly preserveOrder?: boolean | undefined; } & Options

Removed class or interface members

None detected.

Changed class or interface members

None detected.

Newly deprecated

None detected.

Requirement changes (engines, peer dependencies)

BeforeAfter
engines.node^12.20.0 || ^14.13.1 || >=16.0.0>=20

Frequently asked questions

What are the breaking changes when upgrading locate-path from 7 to 8?

Between locate-path 7.2.0 and 8.0.0, Vigia found 0 removed exports, 2 changed signatures and 0 removed or changed class or interface members.

What became deprecated in locate-path 8?

0 exports or members are newly marked as deprecated in locate-path 8.0.0.

For agents

GET https://vigia.coredls.cloud/v1/packages/npm/locate-path/upgrade?from=7.2.0&to=8.0.0