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

@bryophyte/storybook-addon

v0.1.0

Published

Storybook addon for Bryophyte analysis data

Readme

@bryophyte/storybook-addon

Storybook addon that surfaces Bryophyte analysis data inside Storybook. It renders a Bryophyte panel and provides React blocks you can drop into Docs/MDX.

Prerequisites

This addon expects analysis data generated by the Bryophyte CLI. The CLI stores analysis files in a centralized .bryophyte/analyses/ folder at your project root.

Generate analysis data

First, initialize the .bryophyte folder at your monorepo/project root:

bunx bryophyte init <rootPath>

Then analyze the packages you want to track:

bunx bryophyte analyse <projectPath>

This creates files in the structure:

.bryophyte/
  config.json
  analyses/
    _packagename.json           # e.g., _test_package.json
    _other_package.json

The filename is derived from the package name (e.g., @test/package becomes _test_package.json).

Serving analysis data in Storybook

The recommended approach is to serve the .bryophyte folder via Storybook's staticDirs and reference files via analysisUrl:

// .storybook/main.ts
export default {
  staticDirs: ['../public', '.bryophyte'],  // Adjust path based on your structure
  // ...
}

Install

bun add -D @bryophyte/storybook-addon

Storybook setup

Add the addon to .storybook/main.ts:

export default {
  addons: ['@bryophyte/storybook-addon/manager'],
}

Usage (Panel)

Provide Bryophyte data via story parameters using analysisUrl (recommended for monorepos):

export default {
  component: Button,
  parameters: {
    bryophyte: {
      analysisUrl: '/analyses/_test_package.json',  // Served from staticDirs
      componentName: 'Button',
    },
  },
}

Or import the analysis JSON directly:

import analysis from '.bryophyte/analyses/_test_package.json'

export default {
  component: Button,
  parameters: {
    bryophyte: {
      analysis,
      componentName: 'Button',
    },
  },
}

Usage (Docs / MDX block)

import { PropUsageBlock } from '@bryophyte/storybook-addon'
import analysis from '.bryophyte/analysis.json'

<PropUsageBlock
  analysis={analysis}
  componentName='Button'
  title='Button prop usage'
/>

Parameters

  • bryophyte.analysis: Analysis JSON (object or array).
  • bryophyte.analysisUrl: URL to the analysis JSON.
  • bryophyte.packageName: Select from an array of analyses.
  • bryophyte.componentName: Component export name (required).
  • bryophyte.componentFile: Optional file path match for disambiguation.