Vigia

Upgrading pify from 5.x to 6.x

Comparison of the public API of pify 5.0.0 and 6.1.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 exports2
Changed signatures0
Removed class or interface members0
Changed class or interface members0
Newly deprecated0
Requirement changes (engines, peer dependencies)1
New exports8

Removed exports

importexportkindBefore
pifyPifyOptionsinterfaceinterface
pifyPromiseModuleinterfaceinterface

Changed signatures

None detected.

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>=10>=14.16
New exports (8)
importexportkind
pifyOptionstype
pifydefaultfunction
pifyPromisifytype
pifyStringEndsWithtype
pifyInternalOptionstype
pifyPromisifyModuletype
pifyLastArrayElementtype
pifyDropLastArrayElementtype

Frequently asked questions

What are the breaking changes when upgrading pify from 5 to 6?

Between pify 5.0.0 and 6.1.0, Vigia found 2 removed exports, 0 changed signatures and 0 removed or changed class or interface members.

What became deprecated in pify 6?

0 exports or members are newly marked as deprecated in pify 6.1.0.

For agents

GET https://vigia.coredls.cloud/v1/packages/npm/pify/upgrade?from=5.0.0&to=6.1.0