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

essentials-ui

v0.1.0

Published

Pluggable React UI components built on a base UI library, wired through per-component data contracts (ports & adapters).

Readme

essentials-ui

A React wrapper around the Base UI primitives (@base-ui/react), published as an npm package (@essentials/ui). Each component is pluggable: one import, pass the props. Variants are styled with CVA against design tokens; consumed source-agnostically via per-component contracts (built for a separate Mendix widget project).

import { Button, Avatar, userToAvatar } from '@essentials/ui';
import '@essentials/ui/styles.css'; // once, app-wide

<Button label="Save" variant="primary" size="md" onClick={save} />;
<Avatar {...userToAvatar(currentUser)} size="md" />;

Architecture: per-component contracts (ports & adapters)

Every component owns a contract — the inbound port describing exactly the data it needs. Data from any source (API DTO, domain entity, CMS) is mapped into that contract by an adapter, so where the data comes from can change without touching the component.

external source ──(adapter)──▶ component contract ──▶ Component
   User, DTO, …                  ButtonContract           <Button />
  • Contract (*.contract.ts) — the data port. One per component, since each component's expected data differs.
  • Adapter (adapters/*.adapter.ts) — pure (source) => contract mapping.
  • Component (*.tsx) — wraps the Base UI primitive and consumes the contract. This is the only layer that imports @base-ui/react.

The contract is also the integration seam for Mendix: the Mendix widget writes an adapter from its datasource/attribute props to the contract and spreads it — this package never imports Mendix.

const toContract = (p: MyWidgetProps): ButtonContract => ({
  label: p.caption?.value ?? '',
  disabled: p.disabledExpr?.value ?? false,
});
// <Button {...toContract(props)} onClick={() => props.onClick?.execute()} />

Variants & theming

Variants live in *.variants.ts (CVA) and emit semantic classes; styling is plain CSS in src/styles/ driven by --eui-* design tokens. Override those CSS variables to theme — no Tailwind. Import the compiled stylesheet once: import '@essentials/ui/styles.css'.

Scripts

| Command | Description | | -------------------- | -------------------------------------------------- | | npm run dev | Vite playground (dev/) for eyeballing components | | npm run build | Build the library + dist/styles.css | | npm test | Run the Vitest suite once | | npm run test:watch | Vitest in watch mode | | npm run lint | ESLint | | npm run format | Prettier write |

Conventions

  • Files: kebab-case. Components: PascalCase.
  • Stack: React + TypeScript + Vite, tested with Vitest. Variants via CVA.