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

@openuidev/thesys

v0.3.2

Published

Openui-lang based artifacts (Presentation, Report) and Assitant responses

Readme

@openuidev/thesys

OpenUI c1 components for chat, dashboard, presentation, and report surfaces. The public API is what src/index.ts exports — see the repo root CLAUDE.md for the surface contract and monorepo layout.

Stylesheets

One stylesheet ships: @openuidev/thesys/styles.css (compiled from src/styles.scss, KaTeX fonts alongside in dist/fonts/).

It is plain, unlayered CSS — the same convention as @openuidev/react-ui. Override styles the usual way: write a selector of equal or higher specificity later in your cascade. Do not wrap this sheet in a CSS @layer yourself: unlayered styles (react-ui's, your app's) beat all layered styles regardless of specificity, which silently breaks the library's own internal overrides (e.g. context-card image-variant tag styling).

Cascade-layer-based shipping is deliberately parked: layers are young, and Next.js's webpack pipeline mis-serializes @import … layer(name) into a dead @media block, so a layered entry would silently no-op for a large share of consumers. Revisit when cascade layers are better supported across the bundlers consumers use.