Upgrading find-up from 7.x to 8.x

Comparison of the public API of find-up 7.0.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 paths	0
Removed exports	2
Changed signatures	5
Removed class or interface members	0
Changed class or interface members	0
Newly deprecated	0
Requirement changes (engines, peer dependencies)	1
New exports	3

Removed exports

import	export	kind	Before
`find-up`	`pathExists`	function	`(path: string): Promise<boolean>`
`find-up`	`pathExistsSync`	function	`(path: string): boolean`

Changed signatures

export	Before	After
`find-up · findUp`	`(name: string \| readonly string[], options?: any): Promise<string \| undefined> \| (matcher: (directory: string) => Match \| Promise<Match>, options?: any): Promise<string \| undefined>`	`(name: string \| readonly string[], options?: Options \| undefined): Promise<string \| undefined> \| (matcher: (directory: string) => Match \| Promise<Match>, options?: Options \| undefined): Promise<string \| undefined>`
`find-up · Options`	`any`	`{ readonly stopAt?: string \| undefined; readonly type?: "file" \| "directory" \| "both" \| undefined; readonly limit?: number \| undefined; } & Omit<LocatePathOptions, "type">`
`find-up · findUpSync`	`(name: string \| readonly string[], options?: any): string \| undefined \| (matcher: (directory: string) => Match, options?: any): string \| undefined`	`(name: string \| readonly string[], options?: Options \| undefined): string \| undefined \| (matcher: (directory: string) => Match, options?: Options \| undefined): string \| undefined`
`find-up · findUpMultiple`	`(name: string \| readonly string[], options?: any): Promise<string[]> \| (matcher: (directory: string) => Match \| Promise<Match>, options?: any): Promise<string[]>`	`(name: string \| readonly string[], options?: Options \| undefined): Promise<string[]> \| (matcher: (directory: string) => Match \| Promise<Match>, options?: Options \| undefined): Promise<string[]>`
`find-up · findUpMultipleSync`	`(name: string \| readonly string[], options?: any): string[] \| (matcher: (directory: string) => Match, options?: any): string[]`	`(name: string \| readonly string[], options?: Options \| undefined): string[] \| (matcher: (directory: string) => Match, options?: Options \| undefined): string[]`

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`	`>=18`	`>=20`

New exports (3)

import	export	kind
`find-up`	`findDown`	function
`find-up`	`findDownSync`	function
`find-up`	`FindDownOptions`	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 find-up from 7 to 8?

Between find-up 7.0.0 and 8.0.0, Vigia found 2 removed exports, 5 changed signatures and 0 removed or changed class or interface members.

What became deprecated in find-up 8?

0 exports or members are newly marked as deprecated in find-up 8.0.0.

For agents

GET https://vigia.coredls.cloud/v1/packages/npm/find-up/upgrade?from=7.0.0&to=8.0.0