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

@webtretho/webtretho-storybook

v0.0.22

Published

This library is made by Webtretho Frontend Team

Readme

Webtretho Storybook

🔗 What is insided?

🧾 Prerequisites

🛠 How to use

@storybook/cli

npm install -g @storybook/cli

Install and Start

yarn && yarn storybook
# or npm install && npm run storybook  

📌 Scripts

  • test: run all jest tests
  • storybook: Start and launch Storybook. Run storybook on 6006 port
  • lint: Lints and fixes files. run the linter on all components
  • build-storybook: Compiles and minifies for production. Create the build version of storybook

👏 Absolute paths

TypeScript

// anyComponent.tsx
import { Component } from 'packages/Component';
import sass from 'sass/*';

SCSS

// component.module.scss
@import "sass/*";
@import "sass/config/colors";

Read more

🕹 Usage

After publishing our lib (@webtretho/webtretho-storybook) you can import and use the component:

//
import React from 'react'
import { Button } from '@webtretho/webtretho-storybook'

const App = () => {
  render() {
    return <Button />
  }
}

🚀 How to publish the library to NPM

Checkout the latest version of the master branch

git checkout master
git pull

Update the library version number

Can be "major", "minor", or "patch". Almost always use "patch", unless implementing significant changes.

npm version patch

or the following for a prerelease:

npm version prerelease --preid=alpha

Push the newly created version and tag

git push origin <BRANCH> --follow-tags

Build the library

npm run build

Authorize NPM

Add your username, password, email

npm adduser

Publish the library

If this is a standard release of the current major version use:

npm publish

If this is an experimental release, use the "alpha" tag.

npm publish --tag alpha

This will ensure that the "latest" tag doesn't get updated.