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

edk-storybook

v0.0.50

Published

This project uses the web component framework "lit" to create web components following the open-wc standard. The components itself can be found and defined/developed inside the "/src/"-folder. If you create a new component which should be included in th

Readme

Development infos

This project uses the web component framework "lit" to create web components following the open-wc standard. The components itself can be found and defined/developed inside the "/src/"-folder. If you create a new component which should be included in the npm package release, it should be exported inside the ./src/index.ts . To build the webcomponents we use "webpack" and typescript to compile and bundle the webcomponents.

To support webcomponent development, documentation and management we use storybook. To add a lit webcomponent to storybook you need to create a "stories.ts" file for each webcomponent you want to import into storybook. These files should be contained inside the "./stories/" folder. (min example in : ./stories/edk-radiobutton.stories.ts)

Commands :

To run storybook locally (for demoing and development):

npm run storybook

To build for npm:

npm run build:production

To build and publish to npm :

npm publish

Useful developement links

Webcomponent development: Lit webcompnents documentation: https://lit.dev/docs/components/overview/ Documentation for storybook .stories : https://storybook.js.org/docs/react/writing-stories/introduction

Build Tools: Webpack with typescrit : https://webpack.js.org/guides/typescript/#basic-setup

Build information

The build project delivers the file ./dist/package/index.js which includes the bundled webcomponents transpile to es6.

Usage of npm package

Currently the only way to effectivly use the published package with the webcomponents inside Server Side Rendering (SSR) Applications, is to use a CDN to load the npm package at client side and load them at this point.

We will test further other methods to intergrate them at Server side.

Installation

npm i edk-storybook

Usage

In native browser Html Apps:

<script type="module">
  import 'edk-storybook/edk-button.js';
</script>

<edk-button></edk-button>

For SSR Applications :

<script type="module" src="https://unpkg.com/edk-storybook@latest"></script>
<edk-button></edk-button>

Linting and formatting

To scan the project for linting and formatting errors, run

npm run lint

To automatically fix linting and formatting errors, run

npm run format

Testing with Web Test Runner

To execute a single test run:

npm run test

To run the tests in interactive watch mode run:

npm run test:watch

Demoing with Storybook

To run a local instance of Storybook for your component, run

npm run storybook

To build a production version of Storybook, run

npm run storybook:build

Tooling configs

For most of the tools, the configuration is in the package.json to reduce the amount of files in your project.

If you customize the configuration a lot, you can consider moving them to individual files.

Local Demo with web-dev-server

npm start

To run a local development server that serves the basic demo located in demo/index.html