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 paths	0
Removed exports	2
Changed signatures	0
Removed class or interface members	0
Changed class or interface members	0
Newly deprecated	0
Requirement changes (engines, peer dependencies)	1
New exports	8

Removed exports

import	export	kind	Before
`pify`	`PifyOptions`	interface	`interface`
`pify`	`PromiseModule`	interface	`interface`

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)

	Before	After
`engines.node`	`>=10`	`>=14.16`

New exports (8)

import	export	kind
`pify`	`Options`	type
`pify`	`default`	function
`pify`	`Promisify`	type
`pify`	`StringEndsWith`	type
`pify`	`InternalOptions`	type
`pify`	`PromisifyModule`	type
`pify`	`LastArrayElement`	type
`pify`	`DropLastArrayElement`	type

Give your AI agent these facts

Vigia is a free MCP server: your coding agent checks versions, breaking changes and vulnerabilities before it writes code. No signup, no API key.

claude mcp add --transport http vigia https://vigia.coredls.cloud/mcp

Add to Cursor Add to VS Code ★ Star on GitHub

Any other MCP client

{ "mcpServers": { "vigia": { "url": "https://vigia.coredls.cloud/mcp" } } }

Agent skill (SKILL.md): tells the agent when to use Vigia · GitHub Action for pull requests

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