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

@swalvo/live

v0.1.5

Published

Official browser SDK for the Swalvo hosted platform — RTC and chat behind one object. A thin facade over @swalvo/rtc and @swalvo/chat.

Readme

@swalvo/live

Swalvo for the browser, with RTC and chat behind one object.

Part of Swalvo, open-source real-time communication infrastructure.

This is a facade, not a third implementation: swalvo.rtc is a real RTCClient from @swalvo/rtc and swalvo.chat is a real ChatClient from @swalvo/chat. Every method, event and type documented for those packages applies here unchanged, because they are those objects.

Only want calls? Use @swalvo/rtc directly — it pulls in no messaging code. This package is for apps that want both planes without wiring two clients, and it mirrors the shape @swalvo/react-native gives mobile, so the same mental model works on both.

Install

npm install @swalvo/live

Use

RTC and chat credentials are independent, so supply whichever planes your app actually uses:

import { Swalvo } from '@swalvo/live';

new Swalvo({ token, endpoint });                        // calls only
new Swalvo({ chatToken, chatApiUrl });                  // messaging only
new Swalvo({ token, endpoint, chatToken, chatApiUrl }); // both
const swalvo = new Swalvo({ token, endpoint, chatToken, chatApiUrl });

const room = await swalvo.join('room_123');
await room.enableCamera();

await swalvo.chat!.connect({ room: 'room_123' });
await swalvo.chat!.sendMessage({ text: 'Hello' });

Every value comes from your backend's token-mint response — none should be hand-constructed.

Live streaming

swalvo.live is available on every instance regardless of the credentials the instance was built with: host, co-host and viewer tokens are minted per stream, per role, by your backend.

const stream = await swalvo.live.join(credentials);
if (stream.isHost) await stream.room.enableCamera();

Exports

Swalvo, createSwalvo, LiveStream, joinLiveStream, plus re-exported Room, RTCClient, ChatClient, ChatMessage, RTCError types for convenience.

Documentation

License

MIT