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

@xyazi/regua

v0.24.0

Published

A React design system whose rules can't be overridden. Components take data, not styles.

Readme

regua

npm

A React design system, at regua.pt. Documentation at regua.pt/docs, and two clickable products built only from regua: a helpdesk at regua.pt/examples/helpdesk and billing at regua.pt/examples/billing.

Install

npm install @xyazi/regua

Requires React 18 or later.

Use

Import the stylesheet once, at the root of your app, then use the components:

import '@xyazi/regua/styles.css'
import { Page, Stats } from '@xyazi/regua'

export function Overview() {
  return (
    <Page title="Overview" actions={[{ label: 'New project', variant: 'primary' }]}>
      <Stats
        title="This month"
        description="Compared with the previous 30 days."
        items={[
          { label: 'Orders', value: 1284, format: 'number', previous: 1146, better: 'up' },
          { label: 'Returned', value: 4.2, format: 'percent', previous: 5, better: 'down' },
        ]}
      />
    </Page>
  )
}

Theme and mode

Two attributes on <html> set the look of the whole app:

  • data-mode="light" or "dark" forces a mode. Without it, regua follows the operating system.
  • data-theme="<name>" picks a theme. Without it, regua uses Petróleo, which styles.css includes. Every theme ships on its own as @xyazi/regua/themes/<name>.css: import the ones the app needs after styles.css, and switch between them with the attribute.
<html data-theme="petroleo" data-mode="dark"></html>

App settings

ReguaProvider holds the settings regua cannot guess. It is optional; wrap your app in it once:

import { ReguaProvider } from '@xyazi/regua'

export function Root() {
  return (
    <ReguaProvider navigate={(href) => router.push(href)} locale="en-GB" currency="EUR">
      <App />
    </ReguaProvider>
  )
}
  • navigate: in-app links go through your router. Without it, they do a full page load.
  • locale: every number regua shows is formatted for it. Defaults to en-US.
  • currency: the currency of every currency format. Defaults to USD.

Components

AppShell, Page, FieldGroup, FieldRow, TextField, NumberField, Textarea, Switch, Checkbox, Select, Stats, SummaryList, Table, Timeline, AttentionList, AssistantChat and Chart.

A page is one column of sections, straight in the Page, in one order: AttentionList, then SummaryList, Stats and Chart, then FieldGroup, then Timeline, then Table. An AssistantChat takes a page alone. Another order, or anything else in a Page, warns in development.

Upgrading

What to change in your code, version by version, is in CHANGELOG.md.

Develop

npm install
npm run dev        # Storybook on localhost:6006
npm run examples   # the examples on localhost:6007/examples/helpdesk/ and /examples/billing/
npm test
npm run build:site # the site into storybook-static/: the landing, the docs in docs/, the examples

License

MIT