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

@ogygie/ui

v0.35.3

Published

Ogygie front socle: the five prescribed patterns (DataTable, EmptyState, ErrorBanner, ContractForm, VarianceChart), one screen-state component (ScreenState), fetchContract and EditableText. Ships TypeScript sources — Ogygie products run Vite/tsx/vitest by

Readme

@ogygie/ui

Le socle front du framework Ogygie (DECISIONS.md D39) : les briques d'écran que le starter prescrivait sans les livrer. Un produit les IMPORTE ; il ne les recopie plus dans apps/web/src/patterns/, qui ne garde que ses patterns propres. Le paquet livre ses sources TypeScript (comme @ogygie/core) et ne porte aucune chaîne lue par un humain : tout texte lui arrive en prop, traduit par la feature (Lingui).

| Point d'entrée | Ce qu'il porte | Peer | |---|---|---| | @ogygie/ui | ScreenState (accès refusé → erreur → chargement → vide → corps), EmptyState, ErrorBanner, EditableText, Skeleton, fetchContract / createContractFetcher, QueryLike / MutationLike et leurs fixtures | react, zod (@ogygie/core est une DÉPENDANCE, à la version du lockstep) | | @ogygie/ui/data-table | DataTable (colonnes typées, tri, chiffres alignés) + DataTable.Skeleton | @tanstack/react-table (optionnel) | | @ogygie/ui/contract-form | ContractForm (formulaire dérivé d'un contrat Zod) + formFieldsOf | react-hook-form (optionnel) | | @ogygie/ui/variance-chart | VarianceChart (constaté contre référence) + VarianceChart.Skeleton | recharts (optionnel) |

Thème

Les composants portent les utilitaires Tailwind des tokens du starter (surface, surface-raised, border, text, text-muted, accent, accent-contrast, positive, warning, danger, focus, les rayons sm/md/lg). La feuille Tailwind du produit déclare le paquet comme source, sinon ces classes ne sont pas générées :

@import "tailwindcss";
@source "../node_modules/@ogygie/ui/src";

Les couleurs du graphique passent par les variables CSS du thème (--color-accent, --color-text-muted, --color-border).

Un écran

import { ScreenState } from "@ogygie/ui";
import { DataTable } from "@ogygie/ui/data-table";

export function OrdersList() {
  return (
    <ScreenState
      query={useOrders()}
      errorTitle={<Trans>This view could not be loaded</Trans>}
      loading={<DataTable.Skeleton />}
      isEmpty={(data) => data.orders.length === 0}
      emptyState={{ title: <Trans>No order yet</Trans>, explanation: <Trans>Orders appear here once recorded.</Trans> }}
    >
      {(data) => <DataTable rows={data.orders} columns={orderColumns} rowKey={(order) => order.id} />}
    </ScreenState>
  );
}

Le corps d'un écran reçoit des QueryLike et des MutationLike, jamais un hook : il se teste en rendu, sans client de requêtes ni réseau.

Tests

Les tests du paquet tournent sous jsdom (@testing-library/react), un par état de chaque pattern : pnpm vitest run packages/ogygie-ui depuis le repo du framework.