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

@mastondzn/helix

v0.0.2

Published

Tiny Twitch Helix API wrapper based on fetch

Readme

@mastondzn/helix

Tiny Twitch Helix API wrapper based on fetch.

Installation

pnpm install @mastondzn/helix

Usage

import { createHelixClient } from '@mastondzn/helix';

const helix = createHelixClient({
    // you should at least provide your credentials:
    headers: {
        'Client-ID': 'your-client-id',
        Authorization: 'Bearer your-token',
    },

    // these are optional, and the specified values are the defaults:
    // whether to throw non-200 status codes as HTTPError
    throwHttpErrors: true,
    // whether or not you can access paths in camelCase. (customRewards instead of custom_rewards)
    camelCasePath: true,
    // specify any other fetch-compatible function
    fetch: globalThis.fetch,
    // specify another baseUrl
    baseUrl: 'https://api.twitch.tv/helix',
});

const response = await helix.users.get({
    query: { login: ['mastondzn'] },
    // ... other fetch options are also available here
    signal: new AbortController().signal,
});
const body = await response.json();
// body.data is typed correctly for the used endpoint

const response = await helix.channelPoints.customRewards
    .post({
        // enforced query parameters and body shapes
        body: {
            cost: 10_000,
            title: 'foo',
            max_per_stream: 1,
        },
        query: { broadcaster_id: '44601243' },
    })
    .catch((error) => {
        // by default, non-200 status codes throw an HTTPError
        if (error instanceof HTTPError) {
            // error.request is the used request
            // error.response is the response object
        }
    });

Most endpoints should be available, like they appear on the Twitch API Reference. For example, if you need to use the Get Global Chat Badges endpoint, you can access it via helix.chat.badges.global.get(). The url gets built as you access keys on the JavaScript Proxy. This allows for the package's js bundle to be pretty low, while still providing strong type hints.

Acknowledgements