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

@addo-network/design-system

v0.12.8

Published

Addo Network Design System

Readme

Tech stack

  • ⚛️ Create React App (🛃 TypeScript version)
  • 📚 Storybook JS
  • 🎨 Tailwind CSS (UI components are exported with Tailwind Classes)

Quick start

  1. Add package to your project

    Install the dependency.

    # Install
    yarn add @addo-network/design-system
  2. Import

    Start using the Design System UI components

    // LinkButton.stories.tsx
    import { LinkButton, LinkButtonProps } from '@addo-network/design-system/'
  3. import Design System global style colors to tailwind.config.js

    const designSystem = require('@addo-network/design-system')
    
    module.exports = {
    theme: {
      colors: {
        'neutral-dark': designSystem.styles.colors['neutral-dark'],
        'neutral-gray': designSystem.styles.colors['neutral-gray'],
        'neutral-white': designSystem.styles.colors['neutral-white'],
        success: designSystem.styles.colors.success,
        danger: designSystem.styles.colors.danger,
        warning: designSystem.styles.colors.warning,
        info: designSystem.styles.colors.info,
        muted: designSystem.styles.colors.muted
      }
    }

    typography and icons are also available.

Storybook

Add the Design System components to your project's Storybook. We can do that by updating .storybook/main.js to the following:

// .storybook/main.js
const designSystem = require('@addo-network/design-system')

module.exports = {
  stories: ['../src/**/*.stories.@(js|jsx|ts|tsx)'],
  refs: {
   'design-system': {
     title: 'My design system',
     //👇 The url provided by Chromatic when the Design System was deployed
     url: designSystem.design_system_url,
   },
 },
  addons: [
    '@storybook/addon-links',
    '@storybook/addon-essentials',
    '@storybook/preset-create-react-app',
  ],
};

Philosophy

Design systems should only contain pure and presentational components. These components deal with how UI appears. They respond exclusively to props, do not contain app-specific business logic, and are agnostic to how data loads. These properties are essential in allowing the component to be reusable.

App-specific components that contain business logic should not be included because that hamstrings reuse by requiring consumer projects to have identical business constraints.

Storybook Doc

  1. Storybook tutorials.
  2. Design Systems for Developers tutorial.
  3. Official documentation: Storybook.

TODO:

  • Only have one file of truth, right now we have tailwind.config.js and ./src/components/styleguide/styles.ts
  • Documentation to update the package in your project.
  • Documentation for typography and icons import into your project.
  • Use TailwindCSS Presets https://tailwindcss.com/docs/presets
  • CI/CD with Github actions, NPM auto publish, and Chromatic to host Storybook.

Documentation used to build this Design System

  • https://medium.com/@jchiam/publishing-a-typescript-react-component-to-npm-d3cc15b8d0a2
  • https://www.youtube.com/watch?v=m6Jr6w0W1xw
  • https://storybook.js.org/tutorials/design-systems-for-developers
  • https://rfitz.io/blog/tailwind-with-react/