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 🙏

© 2025 – Pkg Stats / Ryan Hefner

storybook-addon-tailwind-autodocs

v2.0.1

Published

Design system documentation that comes directly from your tailwind config.

Readme

Tailwind Autodocs 🎨

Design system documentation that comes directly from your tailwind config.

Demo: Storybook*

*This uses the index.css file from this project

Features

  • Automatically generates documentation from your Tailwind configuration
  • Supports both Tailwind v3 (tailwind.config.js|ts) and v4 (CSS @theme directive)
  • Works with Hot Module Reloading (HMR); changes to your config are reflected immediately
  • Displays theme colors and typography using Storybook's doc blocks
  • Customizable sections and output format

...and more features that are hopefully coming soon:

  • Adding autodocs for tailwind spacing and screen break points

Requirements

  • Storybook
  • TailwindCSS v3.x or v4.x
  • Vite

Installation

First, install the package.

npm install --save-dev storybook-addon-tailwind-autodocs

Then, register it as an addon in .storybook/main.js, and specify your tailwind configuration path there too.

// .storybook/main.ts

// Replace your-framework with the framework you are using (e.g., react-webpack5, vue3-vite)
import type { StorybookConfig } from '@storybook/your-framework';

const config: StorybookConfig = {
    stories: [
        // ...
        '../src/index.css', // 👈 replace with your tailwind configs path
        // '../tailwind.config.js', // 👈 OR use this for tailwind v3
    ],
    // ...
    addons: [
        '@storybook/addon-essentials',
        'storybook-addon-tailwind-autodocs', // 👈 register the addon here
    ],
};

export default config;

Then, run storybook with npm run storybook

And there you go! You should now see a new category in your storybook called "Tailwind Theme". 🎉

Configuration

You can customise the addon behaviour by passing in optional parameters:

| Option | Type | Default | Description | |------------------|-------------------------------------------------------------------------------------|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | sections | ('Colors'\|'Typography')[] or { name: 'Colors'\|'Typography', path?: string }[] | ['Colors', 'Typography'] | Which theme sections to enable. Only 'Colors' and 'Typography' are valid section names. name is the story identifier and label. path is the sidebar location (uses defaultPath if omitted). | | defaultPath | string | 'Tailwind Theme/' | The default sidebar path prefix. | | | forceSingleDoc | undefined or string or { name: string, path?: string } | undefined | If defined, combines all sections into one story. Can be a string (uses defaultPath) or object with custom name and optional path. Unlike sections, name can be any custom string. |

Examples

The terminology (Category, Folder, Component) is explained in Storybook's documentation here.

Default configuration (no options):

// .storybook/main.ts
const config: StorybookConfig = {
    stories: [
        // ...
        '../src/index.css'
    ],
    addons: [
        // ...
        'storybook-addon-tailwind-autodocs',
    ],
};

Custom Category:

const config: StorybookConfig = {
    stories: [
        // ...
        '../src/index.css'
    ],
    addons: [
        // ...
        {
            name: 'storybook-addon-tailwind-autodocs',
            options: {
               defaultPath: 'Design System/' 
            }
        }
    ],
};

Custom Paths / Sections

const config: StorybookConfig = {
    stories: [
        // ...
        '../src/index.css'
    ],
    addons: [
        // ...
        {
            name: 'storybook-addon-tailwind-autodocs',
            options: {
                sections: [
                    {
                        name: 'Typography',
                        path: 'Design System/Component Box',
                    },
                ],
            }
        }
    ],
};

This will result in only Typography appearing under a component ('Component Box') in a category called 'Design System'. Adding a '/' at the end of the path will result in a folder instead of a component.

Single Combined Document

const config: StorybookConfig = {
    stories: [
        // ...
        '../src/index.css'
    ],
    addons: [
        // ...
        {
            name: 'storybook-addon-tailwind-autodocs',
            options: {
                forceSingleDoc: 'My Theme',
                // The above is same as 
                // forceSingleDoc: {
                //     name: 'My Theme'
                // }
            }
        }
    ],
};

This will result in a single story called 'My Theme' containing both Colors and Typography sections under the category created by defaultPath ('Tailwind Theme'). A path can be defined to place it elsewhere, similar to the sections.