Versions and verification

npm 1.0.7

Released 2026-11-10. Adds game rooms, with latest pointing to 1.0.7.

npm install @deeprespond/im-server-sdk@1.0.7

• Adds im.game: listRegions, createRoom, getRoom, listRooms / iterRooms, listMembers, issueTickets, startRoom, closeRoom, removeMember. Creating, starting and closing a room retry automatically; issuing tickets doesn't (reissuing invalidates the old tickets); removing a player generates an operation_id when none is given and keeps it across retries. The created, accepted and removed fields on results come from the status code. See Game rooms · Server API.
• Callbacks gain types for the 7 game_room.* events; game_room.closed carries each player's online time and billable minutes; see game callback events.
• moderation.checkText checks with keywords and AI moderation together by default, and the result gains provider_skipped; pass with_provider: false for keywords only.
• Fixes the write EPIPE failure under Node.js 24 in the unit test for an oversized body in the Express adapter (a problem in the test itself; SDK behavior is unchanged).
• Passes generated-code consistency, ESLint, type checking, unit and type tests (153), build and package checks; the game room integration test against a local server passes.

npm 1.0.6

Released 2026-11-03. Adds AI conversations, with latest pointing to 1.0.6. Source version 1.0.5 was only used for a test build on 2026-10-23 and wasn't published to npm.

npm install @deeprespond/im-server-sdk@1.0.6

• im.ai adds bot management and streaming replies: startStream starts a reply, writeText, writeReasoning, writeImage, writeFile and writeTool write to it, and finish and fail end it; pipeOpenAI, pipeOpenAIResponses, pipeAnthropic and pipeGemini connect a model's stream directly. See Calling the API.
• The callback handler adds onAIMessage and onAIStreamStopped; when ai.stream_stopped arrives, it triggers the signal of the matching stream in this process automatically.
• Passed generated-code consistency, type checks, build and package checks. After installing the public package, 18 end-to-end tests of AI streaming replies against a local service passed. In the unit tests, two Express adapter cases failed under Node.js 24 with write EPIPE (a problem in the test cases themselves, unrelated to this release's changes); the rest passed.

npm 1.0.1

Released 2026-10-23. A fix for the callback module's exports, with latest pointing to 1.0.1.

npm install @deeprespond/im-server-sdk@1.0.1

• Adds the missing runtime exports EVENT_REQUIRED, EVENT_RAW_PATHS, HOOK_ACTIONS and HOOK_RAW_PATHS from /callback, readable from both ESM and CommonJS.
• Services in the main entry stay type-only exports, fixing declarations that looked like runtime constructors after bundling.
• Adds a check that declared values match runtime exports for every public entry, covering ESM, CommonJS and NodeNext consumers.
• Passed generated-code consistency, type checks, unit tests, build and package checks; 4 optional Redis tests were skipped because no test address was configured. The API protocol is unchanged, so the IM server doesn't need updating for this.

npm 1.0.0

Released 2026-10-22. The public package is @deeprespond/im-server-sdk, with latest pointing to 1.0.0 at first release. The package keeps the UNLICENSED license marker; contact DeepRespond about usage rights.

npm install @deeprespond/im-server-sdk@1.0.0

Area	In 1.0.0
Environment	Node.js 22.17.0 or later; ESM, CommonJS and TypeScript declarations; no runtime dependencies
App APIs	Users, friends, blocklists, groups, messages, conversations, chat rooms, files, push, content moderation, presence, IM calls and standalone RTC channels
Requests	Getting and refreshing the App Token, retries by API category, rate-limit waits, local rate limiting, cancellation, timeouts, paging, batch splitting, and keeping raw JSON
Callbacks	Signature and replay checks, event de-duplication, sync callbacks, secret rotation; adapters for Node HTTP, Express, Koa, Fastify and standard Request in Node.js
Shared storage	ioredis and node-redis adapters for the App Token, nonces and event de-duplication
Package contents	Runtime and type files, README and package.json; scripts and framework examples come from the source repository, which needs repository access

Verified at release

This release was checked on Node.js 22.22.2:

Check	Result
Generated-code consistency, ESLint, Prettier, TypeScript	Passed
Unit and type tests	126 passed, 4 optional Redis tests skipped, no type errors
Integration and callback end-to-end tests against the local conformance test service	15 passed, none skipped
ESM and CommonJS build and packing	Passed; 12 packing checks covering publint, attw, NodeNext types, dual-module interop and process exit
Installing from public npm	Installed from the official registry in a standalone project; 9 entries each for ESM and CommonJS, dual-module interop and NodeNext strict type checks passed
Package integrity	The npm registry's SHA-1 and SHA-512 match the checked release package

These results cover the local test service and package integration, not full business verification in every deployment. At release no optional test Redis was configured, TypeScript 5.2 and NestJS 10 compatibility weren't tested specifically, and permission isolation, client messaging and the full callback flow on real cloud apps weren't covered. After integrating, verify in your own test app with the quickstart and local callback testing.

Switching from a local tgz to npm

If you previously used deeprespond-im-server-sdk-1.0.0.tgz built from source, run this page's latest npm install command in the same project to switch the dependency to the public package. Commit the updated package.json and lockfile, and deploy with your project's usual locked install.

Confirm the actual version and source:

npm ls @deeprespond/im-server-sdk
node -p "require('@deeprespond/im-server-sdk/package.json').version"

Package URLs in the lockfile should come from registry.npmjs.org or a mirror your project explicitly configures and trusts. If a private mirror hasn't synced yet, pass --registry=https://registry.npmjs.org/ for this install.

Upgrading later

Projects can pin @deeprespond/im-server-sdk@1.0.7 and commit the lockfile. Before upgrading, read that version's notes and verify the APIs, callbacks and framework config in a test app before updating the dependency. Packages you build from source must be rebuilt and reinstalled; they don't change with the public npm package.

The standalone RTC channel APIs and 9 channel events are included from 1.0.0. For how channel management and users joining media divide up, see Channel methods and Using standalone channels.