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

@q3-technology/design-system-q3

v1.0.30

Published

Q3 Storybook Design System

Downloads

5

Readme

Custom Design System

This is a custom design system, using :

From this tutorial and video

How to

Add a component/module/template

To add a component, it is in the :

  • src/components
  • src/modules
  • src/templates

Add a folder (CamelCase convention), for exemple :

src/components/Button
  1. Inside this folder you must have the Component.txs, Component.stories.tsx and the index.ts. The index.ts is used to export the component :

    export { default } from "./Button";

  2. Inside the src/components folder you must have an index.ts to export each component inside :

    export { default as Button } from "./Button"
    export { default as ButtonVariant } from "./ButtonVariant"
    ...etc

  3. Finally if there are more type of component folders (like components, modules, templates, etc) inside the src/. You must hava a last index.ts inside src/

src/index.ts
export * from "./components";
export * from "./modules";

This should be like this :

├── src
│   ├── components
|   │   ├── Button
|   |   │   ├── Button.tsx
|   |   │   └── index.ts
|   │   └── index.ts
│   └── index.ts
├── package.json
└── package-lock.json

Update the library

When a change is done, there are 5 steps to do :

  1. Update the version inside package.json (following the semantic versioning)
    "version": "1.0.13" --> "version": 1.0.14"
  2. Commit and push the changes on GitHub or BitBucket
    git add all
    git commit -m 'added component'
    git push ...
  3. Run the bundler Rollup
    npm run rollup
  4. Publish the package
    npm publish
  5. Finally update the version inside your project package.json and re-run
    npm install

Use the design system

To use the design system, you just have to install the package like any npm package :
npm install @Your_Github_Name/Your_repo_name
Then import the component you need in the App :
import { Button } from '@Your_Github_Name/Your_repo_name