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 🙏

© 2024 – Pkg Stats / Ryan Hefner

tmi-cluster

v1.0.1

Published

Manages multiple TMI.js instances

Downloads

2

Readme

tmi-cluster

Features

  • Provides an API endpoint almost identical to tmi.js
  • Manages a cluster of anonymous Twitch IRC connections for unlimited read access
  • Utilizes authorized bot account for write access
  • Mocks join and part events using more reliable tmi.twitch.tv endpoint

Usage

Minimal Example

import tmi from 'tmi.js';
import cluster from 'tmi-cluster';

const client = cluster(tmi).Client({
  identity: {
    username: 'botname',
    password: 'oauth:abcdefxyz..'
  },
  channels: [ '#example_user' ]
});

await client.connect();

client.say('#example_user', 'hello :)');

Cluster Configuration

const client = cluster(tmi).Client({
  identity: {
    username: 'botname',
    password: 'oauth:abcdefxyz..'
  },
  cluster: {
    // how many anonymous connections to keep open
    connections: 10,

    // whether ot not IRC join / part messages shall be
    // replaced by more reliable tmi.twitch.tv endpoint
    mock_membership: true,

    // only applies if mock_membership is true
    // determines how many seconds it should wait before fetching
    // the same list of chatters
    membership_timer_local: 20000,

    // only applies if mock_membership is true
    // determines how many seconds it should wait between fetching
    // different lists of chatters
    membership_timer_global: 20
  }
});

Noticeable Differences to tmi.js

  • Has to be initialized with login credentials. Purely anonymous connections are not possible. Authentication via @twurple/auth-tmi also works if respective API is provided instead of tmi.js
  • client.ping() will return reply from authenticated connection.
  • Additional client.pingAll() method that pings every connection. Reply from authenticated connection is the first entry.
  • client.readyState() will return reply from authenticated connection.
  • Additional client.readyStateAll() method that returns array of all ready states. Reply from authenticated connection is the first entry.
  • [Only when using mock_membership = true] Additional client.chatters(channel) method that returns cached list of viewers connected to chat. This is the exact reply from tmi.twitch.tv
  • [Only when using mock_membership = true] client.on('join', callback) provides an additional callback parameter, indicating the user group of the joined chatter (broadcaster, vips, moderators, staff, admins, global_mods, viewers)