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

calling-signaling

v0.1.4

Published

A WebRTC signaling server supporting calling

Readme

calling-signaling

What is this?

This is a (WebRTC) signaling server with support for calling. It is developed and tested with rtc-lib.

  • rooms
    • abstraction of a multi or single user signaling session
    • support of multiple rooms using one connection
  • status objects
    • status on rooms and users
    • can be changed during a session and will be updated on other clients
    • users have a global state which can be overwritten in rooms
  • namespaces
    • used to announce users and rooms
    • subscribe to get updates on a namespace
    • register to get announced to subscribers
    • subscribers will receive messages on new users/rooms and changed state
    • can be subscribed to multiple namespaces
    • can be registered to multiple namespaces
  • invitations
    • invite users into a room
    • invited users will be listed in the room as pending
    • can be accepted or denied by receiving user
    • can be cancelled by sending user
  • protocol
    • can be used over any channel with any serialization
    • JSON over WebSockets transport layer included
    • requests receive an answer or an error message from the server
    • async handling using transaction ids
  • modularized
    • each feature (rooms, invitations, ...) is implemented in seperate module
    • as few dependencies as possible
    • easily extendable
    • feature set can be adapted to use case

How to use?

Standalone with npm

Install with

npm install -g calling-signaling

And run with

calling-signaling

Standalone from git

Install the dependencies with

npm install

and run the server with

coffee src/main.coffee

As library

To integrate the library into you node project install with

npm install calling-signaling

And require in your source files

var calling = require('calling-signaling')
new calling.CallingWebsocketServer(8080, "0.0.0.0")

You can also integrate the signaling server into express

var calling = require('calling-signaling');

var calling_server = new calling.CallingServer();

require('express-ws')(app);
app.ws('/signaling', function(ws) {
    var channel = new WebsocketChannel(ws);
    calling_server.create_user(channel);
});

You can create servers with custom transports, custom feature sets and integrate your own modules. See calling_server.coffee to find out how to write your own server.