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

@johnb08/test-library

v1.0.22

Published

test-library

Readme

Kodehode Library Template

Dette er et tomt template library for Kodehode, for å teste hvordan NPM package publishing fungerer, samt hvordan komponent libraries er satt opp.

Det er satt opp for å automatisk publishe til et npm namespace når det blir gjort en pullrequest til Main branch.

Det har Storybook implementert som devDependency som gjør utvikling av komponenter lettere og mer oversiktlig.

Det publisher til @johnb08/test-library, men dette kan endres etterhvert som det taes i bruk i package.json.

Jeg har nettopp forket denne repositorien, hva gjør jeg?

        1. I terminal, kjør npm install, dette skal installere alle dependencies denne repoen trenger.

        2. Hvis install kjørte uten problemer, kan du kjøre npm run storybook for å åpne dokumentasjonsprogrammet. Her kan du også se på hvordan de forskjellige componentene skal settes opp, og hvordan man tester de i et dummy prosjekt etter man er fornøyd med arbeidet i storybook.
        .storybook inneholder mange forskjellige guides til hvordan å bruke, builde og publishe librariet.

        3. Når du er fornøyd med komponenten som er laget, gjør en pullrequest til dev branch. Dette gjør ting oversiktlig, og librariet trenger ikke bli publisert på nytt hver gang en liten komponent blir addet, men kan releases som en større pakke.