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

@pathscale/ui

v3.2.4

Published

Highly opinionated SolidJS component library — batteries and kitchen sink included, but optimized and shiny.

Readme

@pathscale/ui

Highly opinionated SolidJS component library — batteries and kitchen sink included, but optimized and shiny.

101 component families. HeroUI-parity API, daisyUI-style theming, Tailwind v4 tokens, light and dark themes built in.

→ Browse every component, live

Install

bun add @pathscale/ui solid-layouts
bun add -d rsbuild-plugin-solid-layouts
npm install @pathscale/ui solid-layouts && npm install -D rsbuild-plugin-solid-layouts
pnpm add @pathscale/ui solid-layouts && pnpm add -D rsbuild-plugin-solid-layouts
yarn add @pathscale/ui solid-layouts && yarn add -D rsbuild-plugin-solid-layouts

Setup

@pathscale/ui 3.x is a compiled Layout bundle. Configure the application compiler before Solid transforms JSX:

import { pluginBabel } from "@rsbuild/plugin-babel";
import { pluginSolid } from "@rsbuild/plugin-solid";
import { defineConfig } from "@rsbuild/core";
import { pluginSolidLayoutsApplication } from "rsbuild-plugin-solid-layouts";

export default defineConfig({
  plugins: [
    pluginSolidLayoutsApplication({ layouts: ["@pathscale/ui"] }),
    pluginBabel({ include: /\.(?:jsx|tsx|ts)$/ }),
    pluginSolid(),
  ],
});

The Layout plugin must run before Solid. A missing package, manifest, recipe, compiler, or runtime is an error; there is no uncompiled fallback.

Two imports. Everything comes from the root barrel, and one stylesheet is all you needindex.css pulls in the base styles, both themes and the icon set:

import { Button, Flex } from "@pathscale/ui";
import "@pathscale/ui/index.css";

export const Example = () => (
  <Flex direction="col" gap="sm">
    <Button variant="solid" flavor="primary" size="md">Primary</Button>
  </Flex>
);

In the application's Tailwind v4 stylesheet, register the package as a source (adjust the relative path from that stylesheet):

@source "../node_modules/@pathscale/ui";

This includes the published dist/responsive-classes.txt scanner input. Grid and Flex compose responsive classes at runtime, so scanning only the compiled JavaScript misses utilities such as md:grid-cols-3.

Theming

Two themes ship with the library: light (the default when no attribute is set) and dark. Switch globally by setting an attribute on the document:

document.documentElement.setAttribute("data-theme", "dark");

Every component also accepts a dataTheme prop, rendered as data-theme on that element — use it to scope a theme to one subtree.

Tokens are CSS custom properties: --color-primary, --color-base-100, --radius-field, and a glass set among others. index.css includes a Tailwind v4 @theme block, so in a Tailwind v4 app the usual utilities — bg-primary, text-base-content, bg-base-100 — work against them directly.

Components

| family | components | |---|---| | Layout | Flex, Grid, Join, Surface, Card, GlassPanel, Separator, ScrollShadow, Skeleton, EmptyState, Footer, Header, Navbar, Toolbar, FloatingDock | | Typography & misc | Text, Link, Kbd, Badge, Chip, Tag, TagGroup, Avatar, Icon, Tooltip, Breadcrumbs, Pagination, Meter, ProgressBar, ProgressCircle, Spinner | | Inputs | Input, InputGroup, InputOTP, TextField, TextArea, NumberField, SearchField, PasswordField, ColorField, Checkbox, CheckboxGroup, Radio, RadioGroup, Toggle, Slider, Select, ComboBox, ListBox, SizePicker | | Forms | Form, Fieldset, Label, Description, ErrorMessage, FieldError, PasswordRequirements | | Dates | Calendar, RangeCalendar, DatePicker, DateRangePicker, DateField, TimeField | | Color | ColorPicker, ColorArea, ColorSlider, ColorSwatch, ColorSwatchPicker, ColorWheelFlower, ThemeColorPicker | | Overlays | Modal, Drawer, Popover, Dropdown, Menu, Toast, Alert, Disclosure, DisclosureGroup, Accordion | | Data | Table (headless compound + hooks), Tabs | | Auth kit | AuthForm, AuthCard, AuthFieldGroup, AuthSubmitButton, AuthFooterLinks, AuthPoweredBy, AuthErrorMessage, AuthSuccessMessage | | Visual FX | MetalBorder, GlowCard, NoiseBackground, ImmersiveLanding, VideoPreview, LiveChat, ChatBubble, LanguageSwitcher |

All of them rendered and interactive at js.software.

Conventions

The rules that hold across every component — worth two minutes before your first hour:

  • Booleans are HeroUI-style is*: isDisabled, isOpen, isInvalid, isPending, isIconOnly. Native disabled is honored too.
  • Sizes and variants are per-component. Button takes variant (primary | secondary | tertiary | outline | ghost | danger | danger-soft) and size (sm | md | lg); a smaller set of components — Badge, Chip, Avatar, Spinner, Toggle, the progress components — take color instead. Check the component's own types, or the showcase, rather than assuming a shared union.
  • Both class and className work everywhere, and your classes win — they are merged last via twMerge.
  • Controlled/uncontrolled come in triples: isOpen/defaultOpen/onOpenChange, value/defaultValue/onChange. Callbacks pass values, not events.
  • Compound components (Modal.Trigger, Tabs.List, Select.Option) are also exported flat. Parts are styleable via data-slot and state attributes such as data-open.
  • There is no polymorphic as prop.

Forms are built in and take any Standard Schema validator; DataGrid derives filtering, sorting, pagination and selection itself. Both, with toasts, icons and dates, are covered in docs/ui-usage.md.

Requirements

  • SolidJS ^1.9
  • solid-layouts runtime
  • rsbuild-plugin-solid-layouts application compiler integration
  • Tailwind v4 — optional, but required for the @theme token utilities

Migrating from 1.x

1.4.0 is the last pre-Layouts 1.x release. Layout-authored components begin at 2.0.0 and require the setup above. Versions 1.5.0 and 1.6.0 were incorrectly published on the 1.x line and must not be used.

The complete compiler contract, hard-error behavior, commands, and porting analyzer are documented in docs/layouts.md.

Two peers are optional and only needed for the features they back: popmotion (JS animation driver) and @standard-schema/spec (schema validation).

Subpath exports

Everything is available from the root barrel. These exist when you want to be narrower:

import { Button } from "@pathscale/ui/components/button";
import { useAnchoredOverlayPosition } from "@pathscale/ui/hooks/table";
import { runMotion, enablePopmotion } from "@pathscale/ui/motion";

Also @pathscale/ui/hooks/* and @pathscale/ui/styles/*.

The package declares "sideEffects": ["**/*.css"], so bundlers tree-shake what you don't import — the published size is the whole library, not what ships to your users.

Documentation

| | | |---|---| | Live showcase | every component, rendered and interactive | | Usage reference | theming, conventions, forms, table, toast, icons, dates | | Contributing | local setup, component checklist, proposal template | | Releasing | how a push to master becomes an npm version, and the gates it passes |

License

MIT