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

@lewishowles/components

v2.5.0

Published

A library of beautiful components, promoting rapid development, while ensuring that usability and accessibility are at the fore.

Readme

Components

A library of beautiful, heavily-tested components with a focus on accessibility, as well as ease of use for developers and users.

View documentation

Heavily tested?

The goal is to test the components as thoroughly as possible, from unit tests for more complex computed properties, to Playwright simulating user interactions. The library currently sits at >800 Vitest unit tests and >600 Playwright component tests.

Why accessibility?

Accessibility is one of the most important things we can spend time improving. The web is for everyone, and making steps to ensure content is as accessible as possible helps everyone, not just those who need it most.

This library helps improve accessibility in two primary ways; the first by implementing the components with accessibility in mind, so a developer can be confident out of the box; and the second by using the documentation to help promote the mindset of accessibility. In addition, some components show visible errors if standards aren't met, such as form fields requiring labels.

Setup

Automatic imports are recommended. Using unplugin-vue-components and the library's resolver, components are automatically imported only when used:

// vite.config.js
import { componentsResolver } from "@lewishowles/components/resolver";
import Components from "unplugin-vue-components/vite";

export default defineConfig({
	plugins: [Components({ resolvers: [componentsResolver()] })],
});

Named imports and a global Vue plugin are also available. The getting-started guide covers all three, along with overriding components.

Stylesheets

Each component is styled with Tailwind, so each project needs Tailwind (version 4) as well. You also need to import the library styles so component CSS and generated utility classes are available. Import this into your Tailwind entry stylesheet (e.g. main.css):

@import "@lewishowles/components/styles";

The theming guide covers re-colouring the library with your own brand.

Using a component

Once the library is set up, you can use any component by tag anywhere in your app. For example:

<ui-button @click="doMagic">🪄 Bibbidi-Bobbidi-Boo</ui-button>

CLI

The package ships a CLI for discovering and copying component examples without leaving the terminal.

npx @lewishowles/components snippet        # browse and copy a component example
npx @lewishowles/components pattern        # browse and copy a multi-component UI pattern

Run any command with --help for usage details, or --list to see what's available.

Available components

Every component is documented, with live examples, on the documentation site.