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

@s-hirano-ist/s-ui

v2.1.0

Published

Framework-agnostic React 19 design system

Readme

@s-hirano-ist/s-ui

Framework-agnostic design system for React 19 applications. It provides accessible components, interaction primitives, hooks, and a compiled stylesheet. It does not contain Next.js integrations, Server Actions, application forms, content renderers, or product-specific navigation.

Requirements

  • React and React DOM 19
  • A bundler that supports ESM and CSS imports, such as Vite or Next.js

Installation

pnpm add @s-hirano-ist/s-ui react react-dom

Import the compiled stylesheet once at the application entry point. Tailwind CSS is not required by consumers.

import "@s-hirano-ist/s-ui/styles.css";

Components are exposed through direct subpath imports. There is intentionally no root barrel export.

import { Button } from "@s-hirano-ist/s-ui/button";
import { Field, FieldLabel } from "@s-hirano-ist/s-ui/field";
import { Input } from "@s-hirano-ist/s-ui/input";

export function ProfileForm() {
  return (
    <Field>
      <FieldLabel htmlFor="name">Name</FieldLabel>
      <Input id="name" name="name" />
      <Button type="submit">Save</Button>
    </Field>
  );
}

Stateful notifications are scoped to a React root.

import { ToastProvider, useToast } from "@s-hirano-ist/s-ui/toast";

function SaveButton() {
  const toast = useToast();
  return <button onClick={() => toast.success("Saved")}>Save</button>;
}

export function App() {
  return <ToastProvider><SaveButton /></ToastProvider>;
}

Theming

The default theme matches s-private. Override tokens after importing styles.css:

:root {
  --sui-primary: 20 100 180;
  --sui-radius: 0.75rem;
}

Dark mode is enabled by either a .dark ancestor or data-theme="dark". The stylesheet includes no preflight and does not style html or body. Generated utility selectors use the sui: prefix.

Frameworks

Vite applications import the stylesheet in main.tsx before rendering:

import "@s-hirano-ist/s-ui/styles.css";
import { createRoot } from "react-dom/client";
import { App } from "./app";

createRoot(document.getElementById("root")!).render(<App />);

Next.js applications import it from the root layout's global stylesheet:

@import "@s-hirano-ist/s-ui/styles.css";

Router-aware components such as pagination accept normal anchors or a framework link through their polymorphic as prop. The design system itself does not import either framework.

Development and publishing

pnpm --filter @s-hirano-ist/s-ui build
pnpm --filter @s-hirano-ist/s-ui test
pnpm storybook:ui
pnpm storybook:ui:build
pnpm storybook:ui:test
pnpm --filter @s-hirano-ist/s-ui test:consumer
pnpm --filter @s-hirano-ist/s-ui validate:package
pnpm --filter @s-hirano-ist/s-ui publish --access public

The build emits ESM, declaration files, source maps, and dist/styles.css. The source maps remain local build artifacts; the tarball contains only the README, license, JavaScript, declarations, and CSS. Run all validation commands before publishing. publint, Are The Types Wrong, and the Vite consumer fixture validate the publish artifact.