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

@oatfi/ui

v0.3.0

Published

Shared UI primitives, theme contract, and Preview component for OatFi embedded components

Readme

@oatfi/ui

Shared UI primitives, theme contract, and <Preview> component for OatFi embedded components.

Consumed by:

  • onboarding-flow-general (the embedded onboarding microfrontend) — primitives + ThemeProvider
  • oatfi-dashboards — the <Preview> component on the Partner Settings → Branding page

Targets React 19 + MUI 7 + styled-components 6.

Status

Pre-alpha. See /branding-rollout/oatfi-ui-plan.md for the build plan.

  • Step 1 (scaffold + publishing): done. pnpm + semantic-release pipeline mirrors @oatfi/remote-loader (.releaserc.json, .github/workflows/publish.yml).
  • Step 2 (theme contract): done. ThemeProvider, mergeBranding, defaultTheme, useTheme, and the Branding / Theme types live in src/theme/.
  • Step 3 (style bases + Storybook): done. Style bases in src/styles/ (inputs.ts, layout.ts, forms.ts) and Storybook 10 with a branding-driven ThemeProvider decorator. Run pnpm run storybook.
  • Step 4 (form primitives): done. 12 primitives in src/components/ (TextInput, EmailInput, PhoneInput, SSNInput, TaxIdInput, CurrencyInput, DateInput, DropDown, SearchDropdown, FileInput, RadioInput, CheckboxInput) — each with interaction tests and Default/Branded stories. All carry testId/name props and accessible label/error associations for the downstream e2e suite.
  • Step 5 (nav/utility primitives): done. Stepper, Tabs, Loader, DotsMenu in src/components/ (Button lives in src/styles/layout.ts).
  • Step 6 (<Preview>): done. src/preview/Preview.tsx — a self-contained branded snapshot (header, inputs, buttons, stepper) that wraps its own ThemeProvider and takes a branding prop. This is the export the dashboard branding page consumes.
  • Step 7 (build + publish pipeline): done. pnpm run build (Rollup) emits dist/{index.esm.js,index.cjs.js,index.d.ts} with peer deps externalized; CI runs typecheck → test → build → semantic-release. Verified by installing the npm pack tarball into a scratch React 19 project and type-checking the imports.
  • Step 8 (consumer smoke test): remaining — npm link into onboarding-flow-general's Storybook to compare a ported primitive against the original.

Theme usage

import { ThemeProvider } from '@oatfi/ui';

<ThemeProvider branding={{ primaryButtonColor: '#0ea5e9', borderRadius: 12 }}>
  <App />
</ThemeProvider>;

branding is optional and partial — any omitted field falls back to defaultTheme. The provider feeds both styled-components and MUI from the same resolved theme. Configurable fields: primaryButtonColor, secondaryButtonColor, borderRadius, borderWidth, fontFamily (text colors primary/secondary are fixed theme defaults, not partner-configurable).

Scripts

pnpm run typecheck     # tsc --noEmit
pnpm run test          # vitest run
pnpm run test:watch    # vitest (watch)
pnpm run format        # oxfmt write
pnpm run format:check  # oxfmt check

Storybook and the Rollup build are added in later steps of the plan (build/test join CI then).