npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@forinda/video-sdk-signaling-server

v0.1.2

Published

Standalone reference signaling server for the Forinda video SDK (library + CLI)

Readme

@forinda/video-sdk-signaling-server

Standalone reference signaling server for the Forinda RTC SDK. Ships as both:

  • A library (defineSignalingServer({ port })) — drop into any Node app.
  • A CLI (forinda-rtc-signaling --port 3000) — zero-config local server.

Both modes wrap the underlying @forinda/video-sdk-signaling-adapter-ws (Node ws-backed adapter), so they share the same engine + session plumbing.

Install

pnpm add @forinda/video-sdk-signaling-server
# or, for the CLI globally:
pnpm add -g @forinda/video-sdk-signaling-server

The CLI also runs via npx @forinda/video-sdk-signaling-server without a global install.

CLI

forinda-rtc-signaling --help
Usage: forinda-rtc-signaling [options]

Standalone reference signaling server for the Forinda RTC SDK.
Speaks the wire-format protocol from @forinda/video-sdk-signaling-protocol.

Options:
  -V, --version      output the version number
  -p, --port <port>  Bind port (use 0 for OS-assigned) (default: "3000")
  --max-peers <n>    Max peers per room (default: "50")
  -h, --help         display help for command

Examples:

# Default port 3000
forinda-rtc-signaling

# Custom port + room cap
forinda-rtc-signaling --port 8080 --max-peers 20

# OS-assigned port (useful in dev)
forinda-rtc-signaling -p 0

The server logs the bound address and shuts down cleanly on SIGINT/SIGTERM.

Library

import { defineSignalingServer } from "@forinda/video-sdk-signaling-server";

const server = defineSignalingServer({
  port: 3000,
  authenticate: async (token, room) => verifyJwt(token),
  maxPeersPerRoom: 50,
});

console.log("listening on ws://0.0.0.0:3000");

process.on("SIGTERM", async () => {
  await server.close();
});

The returned handle has the same shape as WebSocketSignalingServer from @forinda/video-sdk-signaling-adapter-ws:

interface WebSocketSignalingServer {
  readonly wss: WebSocketServer;
  readonly engine: SignalingEngine;
  readonly session: Session;
  close(): Promise<void>;
}

Options

| Option | Type | Default | Notes | | ----------------- | ----------------------------------------------- | -------------- | ---------------------------------------------- | | port | number | 3000 | Bind port. Use 0 for OS-assigned random. | | engine | SignalingEngine | auto | Bring your own to share state across adapters. | | authenticate | (token?, room) => boolean \| Promise<boolean> | none | Per-join auth check. | | maxPeersPerRoom | number | 50 | Forwarded to the default-constructed engine. | | socketId | (request) => string | randomUUID() | Stable per-connection id. | | extractToken | (request) => string \| undefined | ?token=... | Where the token comes from. |

What this is for

  • Local development: spin up signaling without standing up Express/Hono/Bun.
  • Demos and tests: reproducible, no-config server.
  • Small deployments: <50 concurrent peers, single process.

What this is NOT for

  • Production at scale: no horizontal scaling (no Redis, no shared state). For multi-process deploys, embed @forinda/video-sdk-signaling-adapter-* in your existing infra.
  • HTTPS termination: serve plain ws:// and put a TLS-terminating reverse proxy (nginx, Caddy, Cloudflare) in front of it.
  • Auth beyond a callback: bring your own JWT verifier in authenticate.

Internals

  • Argv parsing: Commander.
  • Color output: picocolors.
  • Bin shim: bin/run.mjs is a tiny ESM entrypoint that imports the compiled dist/cli.js and invokes its main export. Keeping the shim minimal lets the build output evolve without invalidating installed symlinks.

License

MIT — © 2026 Felix Orinda.