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

@wavv/ui

v2.4.16

Published

React UI component library

Readme

Getting Started

Install

// npm
npm i @wavv/ui

// yarn
yarn add @wavv/ui

// pnpm
pnpm add @wavv/ui

Peer Dependencies

@wavv/ui currently has three peer dependencies: react, react-dom, and @emotion/react.

// npm
npm i react react-dom @emotion/react

// yarn
yarn add react react-dom @emotion/react

// pnpm
pnpm add react react-dom @emotion/react

Usage

A ThemeProvider needs to wrap the entire app so that all @wavv/ui components can use those styles.

By default, there is a light and a dark theme on the theme object exported by @wavv/ui. More can be read about the theme and how to customize it here.

import React from 'react';
import { ThemeProvider } from '@emotion/react';
import { theme, ResetStyles, ScrollbarStyles } from '@wavv/ui';

const App = () => {
	const currentTheme = theme.light;
	return (
		<ThemeProvider theme={currentTheme}>
			<ResetStyles />
			<ScrollbarStyles />
			{/* app contents */}
		</ThemeProvider>
	);
};

Documentation

Documentation can be found at ui.wavv.com

For new v2 components, pnpm storybook can be ran to bring up more detailed documentation for props.

Contributing

CLI

When a change is ready to be pushed to the library and published to NPM, the best method is to use the cli.

  1. pnpm cli
  2. Bump version (stick with the pre-release alpha version for now).
  3. Document what changes are going out by answering the cli prompts.
  4. You can answer "no" to the prompt for creating a new branch.
  5. The final prompt asks if you would like to publish to npm. This will handle the alpha version tag for you.

Manual

If something goes wrong with using the CLI, or another change needs to be added to the build before publishing to npm, there are a couple different scripts that can be run to manually build and publish the library.

  1. pnpm build:lib will run another build for the library, ensuring your new changes are included.
  2. Make sure the version in package.json is the new version that should go out if it hasn't already been changed by the cli prompts.
  3. pnpm pub:alpha will publish to npm with the correct alpha tag since we are sticking to a pre-release tag for now.

License

This project is licensed under the terms of the MIT license.