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

@mateosuarezdev/react-ui

v1.0.89

Published

Dynamic React UI library designed to work alongside @mateosuarezdev/react-router

Readme

React UI

@mateosuarezdev/react-ui is the shared React UI toolkit used by the template. It provides styled primitives, form integrations, overlays, and small interaction helpers built around the app's semantic CSS tokens.

Exports

Components

  • Foundation: Button, Icon, Spinner, Divider, Portal, TopLoadingBar.
  • Layout and display: Avatar, AvatarsGroup, ElasticHeader, KeepAlive, LazyImage, List, PageTitle, ShowMoreText, Ups.
  • Selection and overlays: Calendar, Dropdown, MultiSelect, PopoverCard, SearchInput, SegmentedControl, Select, SuperModal.
  • Forms: Form, Input, TextArea, Checkbox, Switch, Tags, WorkingHours, FilePicker, and Submit, including their form-bound counterparts where exposed.

Form and the form-bound controls work with React Hook Form and Zod. Use the standalone controls when the state does not belong to a form.

Feedback and events

  • toast for app notifications.
  • events for the corresponding UI event hooks.

Hooks

  • Interaction: useClickAway, useKeyListener, useLongPress, useMergedRef, useRipple.
  • Environment and layout: useLargeScreen, useNetwork.
  • Overlay positioning: usePopover.

Utilities

  • cn and design helpers for composing semantic classes.
  • Form helpers from utils/forms.
  • focusTrap, the package-wide imperative focus manager.
  • Overflow helpers from utils/overflow.

Overlay and focus conventions

usePopover owns open state, positioning, and click-away behavior. Focus has two deliberately separate responsibilities:

  • Focus containment: temporary modal-like surfaces—such as a DatePicker inside PopoverCard, a dialog, or a drawer—activate the singleton focusTrap for their mounted container. It keeps Tab inside that scope; cleanup restores focus to the prior scope or trigger. The latest active trap owns focus.
  • Roving focus: non-modal option collections—such as Dropdown, Select, and eventually calendar days—move focus between their own options for arrow keys and selection. They do not contain focus: Tab closes or leaves the component and browser navigation continues normally.

A contained popover can use both: the trap owns the boundary, while the calendar controls navigate within it.

Styling

The package expects the consuming app to provide its semantic token classes (for example base, brand, contrast, and state colors). Components expose class-name and color props for app-level composition rather than owning a brand theme.