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

@warmio/ui

v1.2.0

Published

Portable, sealed React components for Warm products.

Readme

@warmio/ui

Portable React components shared by Warm products. Install this package with the exact @warmio/[email protected] CSS contract, import @warmio/design/globals.css once, and add the package's compiled files to Tailwind's source detection:

Why these files are separate

Independently deployed Warm products cannot import runtime code from the private warm-app workspace, so libraries/public-ui/ must be a standalone public package rather than another private workspace entry point. tools/tasks/check-ui-package.mjs is a dedicated package-boundary check because the existing application checks do not build, pack, and inspect a public npm tarball. .github/workflows/publish-ui.yml is separate from application deployment workflows so npm trusted publishing can bind credentials to one reviewable package-release boundary without granting an app deployment permission to publish packages.

@import '@warmio/design/globals.css';
@source '../node_modules/@warmio/ui/dist';

The 1.2.0 public surface contains the Warm badge, logo, Button, Text and StackedDisplay, DropdownMenu, Sheet, the complete responsive Sidebar family, and the ProductHeader composition. ProductHeader owns the responsive frame, breadcrumb/title semantics, leading slot, action slot, and optional portal targets used by Warm product shells. Styling is sealed: use documented semantic properties and layout wrappers, never className or style overrides. DropdownMenu interaction feedback requires the exact public peer [email protected].

The published artifact is standalone and never imports private warm-app workspace packages.