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

@kv-designsystem/react

v1.0.0-alpha.6

Published

This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.

Readme

React + Vite

This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.

Currently, two official plugins are available:

React Compiler

The React Compiler is not enabled on this template because of its impact on dev & build performances. To add it, see this documentation.

Expanding the ESLint configuration

If you are developing a production application, we recommend using TypeScript with type-aware lint rules enabled. Check out the TS template for information on how to integrate TypeScript and typescript-eslint in your project.

Visuell testing lokalt

Alle Storybook-stories kan kjøres som visuelle regresjonstester (screenshot-tester) lokalt via Vitest sin browser mode, med Playwright/Chromium.

Kommandoene under kjøres med pnpm --filter @kv-designsystem/react exec ..., slik at de fungerer fra roten av monorepoet uten å måtte cd inn i @kv-designsystem/react først. Står du allerede inne i @kv-designsystem/react, kan du droppe --filter @kv-designsystem/react exec-delen og bare skrive pnpm vitest ... direkte.

Forutsetning: Playwright må ha lastet ned en Chromium-instans. Hvis det ikke allerede er gjort:

pnpm --filter @kv-designsystem/react exec playwright install chromium

Kjøre testene:

pnpm --filter @kv-designsystem/react exec vitest run --project storybook

Første gang du kjører en story finnes det ingen referanse-screenshot ennå. Vitest oppretter da et nytt bilde under src/**/__screenshots__/ og lar testen feile, slik at du får sjekket bildet før det brukes som fasit. Se over det genererte bildet, og kjør testen på nytt — da sammenlignes et nytt bilde mot referansen (pikseldiff).

Med interaktivt UI: legg til --ui-flagget (og drop run, siden --ui alltid kjører i watch-modus). Åpner en nettleserfane (typisk http://localhost:51204/__vitest__/) hvor du ser testresultater fortløpende, og — ved en feilet skjermbilde-test — får en egen "Attachments"-fane med actual- og diff-bildet side om side:

pnpm --filter @kv-designsystem/react exec vitest --project storybook --ui

Skal du bare følge med på én komponent under utvikling, filtrer på filnavn (fungerer med og uten --ui):

pnpm --filter @kv-designsystem/react exec vitest --project storybook --ui Button

Oppdatere en referanse etter en tilsiktet visuell endring: kjør testen med -u-flagget (Vitest sin vanlige snapshot-oppdatering), så overskrives referansebildet automatisk i stedet for å feile:

pnpm --filter @kv-designsystem/react exec vitest run --project storybook -u

Merk: Disse referanse-screenshotene er gitignored og skal ikke committes. Ordentlig visuell regresjonstesting på tvers av maskiner/nettlesere håndteres av Chromatic i CI (se .github/workflows/publish-chromatic.yml). Bruk de lokale screenshot-testene som en rask sjekk før du pusher.