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

@timmo001/effect-twitch

v2.1.1

Published

Effect client for Twitch: sign-in, Helix, EventSub live notifications and upnext media items

Readme

@timmo001/effect-twitch

An Effect client for Twitch: sign-in, Helix, EventSub stream.online events, and mapping live streams to Up Next media items.

It works on its own and knows nothing about Up Next's config files or socket.

Install

bun add @timmo001/effect-twitch effect
npm install @timmo001/effect-twitch effect
npx jsr add @timmo001/effect-twitch

effect is a peer dependency, so install the same Effect v4 version your app uses.

Sign in

Twitch needs a registered app with a client ID, a client secret and a redirect URL. Send someone to authorizeUrl, then swap the code from the redirect for tokens:

import { authorizeUrl, exchangeCode } from "@timmo001/effect-twitch";

const url = authorizeUrl({ clientId, redirectUri, state });

// Once Twitch redirects back with ?code=...&state=...
const tokens = exchangeCode({ clientId, clientSecret }, { code, redirectUri });

exchangeCode needs an HttpClient, such as FetchHttpClient.layer from effect/http. The only scope requested is user:read:follows.

Client

TwitchClient.layer takes the credentials and tokens. It refreshes the access token before it expires and when Twitch rejects it, and calls onTokens with each new pair so you can store them.

import { TwitchClient, toMediaItem } from "@timmo001/effect-twitch";
import { Effect } from "effect";
import { FetchHttpClient } from "effect/http";

const live = Effect.gen(function* () {
  const twitch = yield* TwitchClient;
  const owner = yield* twitch.validate;
  const streams = yield* twitch.followedStreams(owner.userId);

  return streams.map(toMediaItem);
}).pipe(
  Effect.provide(TwitchClient.layer({ clientId, clientSecret, tokens })),
  Effect.provide(FetchHttpClient.layer),
);
  • validate: checks the token, refreshing it if needed, and returns who it belongs to. Twitch asks apps to do this hourly.
  • users(logins) and streams(logins): look up channels and their live streams, 100 at a time.
  • followedStreams(userId): live streams from followed channels, with viewer counts.
  • followedChannels(userId): every followed channel, live or not.
  • streamOnline(broadcasterIds): a stream of EventSub stream.online events that reconnects forever. It needs a Socket.WebSocketConstructor. Twitch allows up to maxEventSubChannels (10) channels per user token.

Failures are a TwitchError, or a TwitchAuthError when someone needs to sign in again. Neither includes response bodies, so tokens don't end up in logs.

Licence

Apache 2.0. See LICENSE.