Vigia

Upgrading @peculiar/json-schema from 2.x to 3.x

Comparison of the public API of @peculiar/json-schema 2.0.0 and 3.0.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 exports4
Changed signatures0
Removed class or interface members0
Changed class or interface members0
Newly deprecated0
Requirement changes (engines, peer dependencies)1
New exports0

Removed exports

importexportkindBefore
@peculiar/json-schemaIJsonSchemainterfaceinterface
@peculiar/json-schemaJsonTransformclassclass
@peculiar/json-schemaIJsonSchemaIteminterfaceinterface
@peculiar/json-schemaIJsonNamedSchemainterfaceinterface

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>=16.0.0^20.19.0 || >=22.12.0

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 @peculiar/json-schema from 2 to 3?

Between @peculiar/json-schema 2.0.0 and 3.0.0, Vigia found 4 removed exports, 0 changed signatures and 0 removed or changed class or interface members.

What became deprecated in @peculiar/json-schema 3?

0 exports or members are newly marked as deprecated in @peculiar/json-schema 3.0.0.

For agents

GET https://vigia.coredls.cloud/v1/packages/npm/@peculiar/json-schema/upgrade?from=2.0.0&to=3.0.0