Vigia

Upgrading ignore from 6.x to 7.x

Comparison of the public API of ignore 6.0.2 and 7.0.14, computed automatically from their TypeScript types. A changed signature is a candidate for a breaking change, not a certainty.

Summary

Removed import paths0
Removed exports1
Changed signatures0
Removed class or interface members0
Changed class or interface members1
Newly deprecated0
Requirement changes (engines, peer dependencies)1
New exports5

Removed exports

importexportkindBefore
ignoredefaultfunction(options?: Options | undefined): Ignore

Changed signatures

None detected.

Removed class or interface members

None detected.

Changed class or interface members

memberBeforeAfter
Ignore.add(patterns: string | Ignore | readonly (string | Ignore)[]): Ignore(patterns: string | PatternParams | Ignore | readonly (string | Ignore)[]): Ignore

Newly deprecated

None detected.

Requirement changes (engines, peer dependencies)

BeforeAfter
engines.node>= 4—
New exports (5)
importexportkind
ignorePathnametype
ignoreIgnoreRuleinterface
ignoreTestResultinterface
ignoreisPathValidfunction
ignorePatternParamsinterface

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 CursorAdd 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 ignore from 6 to 7?

Between ignore 6.0.2 and 7.0.14, Vigia found 1 removed exports, 0 changed signatures and 1 removed or changed class or interface members.

What became deprecated in ignore 7?

0 exports or members are newly marked as deprecated in ignore 7.0.14.

For agents

GET https://vigia.coredls.cloud/v1/packages/npm/ignore/upgrade?from=6.0.2&to=7.0.14