Vigia

Upgrading @ably/chat from 1.x to 2.x

Comparison of the public API of @ably/chat 1.4.0 and 2.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 exports0
Changed signatures2
Removed class or interface members1
Changed class or interface members1
Newly deprecated0
Requirement changes (engines, peer dependencies)4
New exports1

Removed exports

None detected.

Changed signatures

exportBeforeAfter
@ably/chat · ChatClientclassinterface
@ably/chat · PresenceMemberOmit<Ably.PresenceMessage, "id" | "action" | "timestamp"> & { updatedAt: Date; data: JsonObject | undefined; extras: JsonObject | undefined; userClaim?: string | undefined; }Omit<Ably.PresenceMessage, "id" | "action" | "timestamp" | "memberKey"> & { updatedAt: Date; data: JsonObject | undefined; extras: JsonObject | undefined; userClaim?: string | undefined; }

Removed class or interface members

memberimportBefore
ChatClient.realtime@ably/chatAbly.Realtime

Changed class or interface members

memberBeforeAfter
ChatClient.constructor(realtime: Ably.Realtime, clientOptions?: ChatClientOptions | undefined): ChatClient

Newly deprecated

None detected.

Requirement changes (engines, peer dependencies)

BeforeAfter
engines.node>=20.0.0>=22.0.0
peerDependencies.ably^2.19.0—
peerDependencies.@ably/pubsub-device—^3.0.0
peerDependencies.@ably/pubsub-server—^3.0.0
New exports (1)
importexportkind
@ably/chatcreateChatClientvariable

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 @ably/chat from 1 to 2?

Between @ably/chat 1.4.0 and 2.0.0, Vigia found 0 removed exports, 2 changed signatures and 2 removed or changed class or interface members.

What became deprecated in @ably/chat 2?

0 exports or members are newly marked as deprecated in @ably/chat 2.0.0.

For agents

GET https://vigia.coredls.cloud/v1/packages/npm/@ably/chat/upgrade?from=1.4.0&to=2.0.0