@azure/communication-signaling

中文文档
1.0.0-beta.34发布于 2025/06/21MITTypeScriptCommonJS近 30 天下载 19.3万

Azure Communication Signaling Client

原始使用文档
文档目录11 节
  1. Getting started
  2. Prerequisites
  3. Installing
  4. Browser support
  5. Key concepts
  6. SignalingClient
  7. Examples
  8. Initialize SignalingClient
  9. Enable real-time notifications
  10. Disable real-time notifications
  11. Register listener to events

Azure Communication Signaling client library for JavaScript

The Azure Communication Signaling client library lets developers add real-time notifications for receiving new/update/delete chat message events, typing indicator event, read receipt event, and chat thread events.

Read more about Azure Communication Services here

Getting started

Prerequisites

Installing

npm install @azure/communication-signaling

Browser support

JavaScript Bundle

This client library is only supported in the browser. To use this client library, first you need to use a bundler. For details on how to do this, please refer to our bundling documentation.

Key concepts

SignalingClient

SignalingClient is the primary interface for developers using this client library. It provides methods to enable/disable real-time notifications and register listeners for different events.

Examples

Initialize SignalingClient

Use user access token and Azure logger to initialize signaling client.

import { CommunicationSignalingClient } from '@azure/communication-signaling';
import { AzureCommunicationTokenCredential } from "@azure/communication-common";
import { createClientLogger } from "@azure/logger";

let userAccessToken = '<USER_ACCESS_TOKEN>';
let tokenCredential = new AzureCommunicationTokenCredential(userAccessToken);
let logger = createClientLogger("communication-signaling");
let signalingClient = new CommunicationSignalingClient(tokenCredential, logger);

Enable real-time notifications

signalingClient.start();

Disable real-time notifications

signalingClient.stop();

Register listener to events

With real-time signaling, you can subscribe to listen for new incoming events and call your own business logic accordingly.


// register listener to new incoming message event
signalingClient.on("chatMessageReceived", (payload) => {
    console.log("Notification chatMessageReceived!");
    // your code here
});

// register listener to typing indicator event
signalingClient.on("typingIndicatorReceived", (payload) => {
    console.log("Notification typingIndicatorReceived!");
    // your code here
});

// register listener to thread deleted event
signalingClient.on("chatThreadDeleted", (payload) => {
    console.log("Notification chatThreadDeleted!");
    // your code here
});

版本与发布记录

@azure/communication-signaling 共发布 33 个版本,首次发布于 2020/09/22;过去 12 个月发布了 0 个版本。

版本发布日期距今
1.0.0-beta.34latest2025/06/211.4 年前
1.0.0-beta.332025/05/131.5 年前
1.0.0-beta.322025/02/201.7 年前
1.0.0-beta.312025/01/221.8 年前
1.0.0-beta.292024/10/182 年前
1.0.0-beta.282024/08/022 年前

关于 @azure/communication-signaling 的常见问题

@azure/communication-signaling 是什么?

Azure Communication Signaling Client

如何安装 @azure/communication-signaling?

在项目目录运行 npm install @azure/communication-signaling,或使用 pnpm add / yarn add / bun add。

@azure/communication-signaling 支持 TypeScript 吗?

支持。包内自带 TypeScript 类型声明(package.json 声明了 types 入口),安装后即可获得类型提示,无需再安装 @types 包。

@azure/communication-signaling 支持 ESM 还是 CommonJS?

以 CommonJS 形式发布,可以直接 require();在 ES Module 项目中也可以用 import 引入(Node.js 会把 module.exports 作为默认导出)。

@azure/communication-signaling 需要什么版本的 Node.js?

package.json 的 engines 字段要求 Node.js >=8.0.0。版本不符时 npm 默认只给出警告,开启 engine-strict 后会拒绝安装。

@azure/communication-signaling 可以商用吗?

@azure/communication-signaling 使用 MIT 许可。宽松许可:允许商业使用、修改和再分发,通常只需在分发时保留原版权与许可声明。以上为概括,不构成法律意见,请以许可原文为准。

@azure/communication-signaling 的下载量有多少?

根据 npm 官方下载统计,@azure/communication-signaling 在 2026/10/08 – 2026/11/06 这 30 天内被下载 192,847 次,日均约 6,428 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

@azure/communication-signaling 还在维护吗?

最新版本 1.0.0-beta.34 发布于 2025/06/21(1.4 年前);至今共发布 33 个版本,其中过去 12 个月发布了 0 个;首次发布于 2020/09/22。发布频率只是参考信号:功能稳定的工具可能很少需要更新,建议结合源码仓库的 issue 和提交记录判断。