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

@tailmantic/ui-components

v0.2.2

Published

Standalone React components styled with Tailmantic.

Readme

@tailmantic/ui-components

Standalone React components styled with Tailmantic. All 47 Tailmantic UI components and their base styles live in this package; interactive showcase content and demo-only styles remain in the example application.

Install the package and its peer dependencies:

npm install @tailmantic/ui-components tailmantic react react-dom

Install @popperjs/core too if you use Popper, Popover, or Menu:

npm install @popperjs/core
import { Button, Checkbox, Chip, Dialog, Tabs, TextField } from '@tailmantic/ui-components';

function Example() {
  return (
    <>
      <Button variant="outlined">Cancel</Button>
      <Button color="success">Save</Button>
      <label><Checkbox defaultChecked /> Receive product updates</label>
      <Chip color="primary">React</Chip>
      <TextField label="Project name" />
      <Tabs
        tabs={[{ label: 'Overview', content: 'Project overview' }, { label: 'Activity', content: 'Recent activity' }]}
      />
      <Dialog open={false} onClose={() => {}}>Dialog content</Dialog>
    </>
  );
}

The package requires Node.js 20+ to build or publish. Consuming applications must provide React and React DOM 18+, Tailmantic 1.0+, and @popperjs/core 2.11.8+ when using Popper, Popover, or Menu. Configure the Tailmantic Vite plugin and import virtual:tailmantic.css; add @tailmantic/ui-components/styles to the application's Tailmantic manifest to register the package's base styles. Every component is available from the root entry, has its own subpath export, and includes TypeScript props:

import Button from '@tailmantic/ui-components/button';
import Tabs from '@tailmantic/ui-components/tabs';

For example, Checkbox supports native input props, controlled or uncontrolled state, and an indeterminate state. Its ref points to the native input element.

Accordion

Accordion is a compound component. Each item owns its controlled or uncontrolled expanded state, while AccordionHelper and AccordionToolbar are optional parts of the shared layout:

import { useState } from 'react';
import {
  Accordion,
  AccordionHelper,
  AccordionItem,
  AccordionToolbar,
} from '@tailmantic/ui-components';

function SettingsAccordion() {
  const [notificationsExpanded, setNotificationsExpanded] = useState(false);

  return (
    <Accordion>
      <AccordionToolbar>Workspace settings</AccordionToolbar>
      <AccordionItem title="Profile" defaultExpanded>
        Manage your workspace profile.
      </AccordionItem>
      <AccordionItem
        title="Notifications"
        expanded={notificationsExpanded}
        onChange={setNotificationsExpanded}
      >
        Choose which updates to receive.
      </AccordionItem>
      <AccordionHelper>Select a section to reveal its details.</AccordionHelper>
    </Accordion>
  );
}

Autocomplete

Autocomplete supports controlled or uncontrolled single selection, multiple selections, and custom free-solo values:

import { Autocomplete } from '@tailmantic/ui-components';

<Autocomplete
  options={[
    { label: 'React', value: 'react', description: 'UI library' },
    { label: 'Vue', value: 'vue', description: 'UI framework' },
  ]}
  value={framework}
  onValueChange={setFramework}
/>;

Set multiple and use selectedValues/onSelectedValuesChange for a removable selection list. Set freeSolo to offer a custom option when the query does not match an existing label. Both modes support keyboard navigation and work with string options as well as { label, value, description } objects.

Standalone component usage

Each component ships its own style file and a corresponding token file so you can load only what you need.

// Load tokens (design variables) and styles for a single component
import '@tailmantic/ui-components/tokens/dark';  // or /tokens/light
import '@tailmantic/ui-components/button/styles';

// Or register every component's styles at once (existing approach)
import '@tailmantic/ui-components/styles';

Token files (/tokens/dark, /tokens/light) set CSS custom properties — colors, spacing, border radii, shadows — on :root. They are the design-token layer that all component styles reference via var(--...) variables. Import exactly one token file per page.

Customizing tokens — override any CSS variable in your own stylesheet after the token import:

:root {
  --color-primary: #7c3aed;
  --radius-md: 0.5rem;
}

Mix and match — you can import styles for only the components your page uses. Each */styles file is self-contained and registers its tokens with Tailmantic's collector independently.

ButtonGroup dependency — ButtonGroup renders Button children and its styles target rgi-button descendants. Always import button/styles alongside button-group/styles:

import '@tailmantic/ui-components/button/styles';
import '@tailmantic/ui-components/button-group/styles';