Upgrading p-locate from 6.x to 7.x
Comparison of the public API of p-locate 6.0.0 and 7.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 | 2 |
| 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 |
|---|---|---|
p-locate · Options | interface | { readonly concurrency?: number | undefined; readonly preserveOrder?: boolean | undefined; } |
p-locate · default | <ValueType>(input: Iterable<ValueType | PromiseLike<ValueType>>, tester: (element: ValueType) => boolean | PromiseLike<boolean>, options?: Options | undefined): Promise<ValueType | undefined> | <ValueType>(input: Iterable<ValueType | PromiseLike<ValueType>>, tester: (element: ValueType) => boolean | PromiseLike<boolean>, options?: Options | undefined): Promise<ValueType | undefined> | <ValueType>(input: AsyncIterable<ValueType | PromiseLike<ValueType>>, tester: (element: ValueType) => boolean | PromiseLike<boolean>): Promise<ValueType | undefined> |
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 | ^12.20.0 || ^14.13.1 || >=16.0.0 | >=20 |
Frequently asked questions
What are the breaking changes when upgrading p-locate from 6 to 7?
Between p-locate 6.0.0 and 7.0.0, Vigia found 0 removed exports, 2 changed signatures and 0 removed or changed class or interface members.
What became deprecated in p-locate 7?
0 exports or members are newly marked as deprecated in p-locate 7.0.0.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/p-locate/upgrade?from=6.0.0&to=7.0.0