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

storybook-addon-github-issues

v0.0.10

Published

Display related github issues for a component

Readme

Github issues for Storybook

Track issues logged against specific components in your repository

Getting Started

yarn add -D storybook-addon-github-issues

Add the following into your .env file:

GITHUB_REPOSITORY=username/repo
GITHUB_TOKEN=your_auth_token

...where your_auth_token is a Github personal access token with at least the repo scope. This will be used to access Github's GraphQL API to retrieve matching stories.

Add storybook-addon-github-issues to the addons list in .storybook/main.js.

In your .storybook/preview.js:

addParameters({
  issues: {
    repository: process.env.GITHUB_REPO,
    token: process.env.GITHUB_TOKEN,
  },
});

Tagging stories

By default, issues must have labels matching the name of the story, in kebab case. For example, if your component story is Atoms/Button, then you should tag your issues with button.