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

@playaos/ui-kit

v0.2.2

Published

PlayaOS branded components — fully themed, ships precompiled CSS

Readme

@playaos/ui-kit

Fully PlayaOS-branded React components — ships precompiled CSS for design tokens. Re-exported components from @playaos/ui-default still require Tailwind CSS.

Choosing the right package

| Package | Style | When to use | |---------|-------|-------------| | @playaos/ui | Unstyled | Bring your own design system | | @playaos/ui-default | Vanilla Tailwind | Shadcn-style, easy to override | | @playaos/ui-kit | PlayaOS branded | Drop-in PlayaOS look and feel |

Install

npm install @playaos/ui-kit @playaos/ui

Usage

Import the stylesheet once at your app's entry point:

import "@playaos/ui-kit/style.css";

Then use components:

import { PlanLimitAlert, DataTable, DirectoryProfileCard } from "@playaos/ui-kit";

Design tokens

All brand values are CSS custom properties defined in style.css. Override any token in your own CSS:

:root {
  --playaos-color-primary: #6366f1; /* swap orange for indigo */
}

| Token | Default | Description | |-------|---------|-------------| | --playaos-color-primary | #f97316 | Brand orange | | --playaos-color-secondary | #1e293b | Dark slate | | --playaos-color-accent | #fed7aa | Soft orange tint | | --playaos-color-border | #e2e8f0 | Neutral border | | --playaos-color-muted | #f8fafc | Background muted | | --playaos-radius-md | 0.5rem | Standard corner radius |

Waffles appearance pack

@playaos/ui-kit/appearance/waffles.css re-skins the kit with the Waffles Admin brand (PLA-1190). It is an opt-in token overlay — a DaisyUI waffles-light theme plus a waffles-dark companion and the matching --playaos-* overrides — not a fork. Import it into your Tailwind entry after the kit styles, then mark the root element:

/* globals.css */
@import "@playaos/ui-kit/appearance/waffles.css";
<html data-theme="waffles-light" data-playaos-appearance="waffles">
  • data-theme="waffles-light" / "waffles-dark" activates the DaisyUI theme and the kit tokens together.
  • data-playaos-appearance="waffles" activates the light kit tokens on its own, for consumers that render the kit without DaisyUI themes.

The pack declares DaisyUI themes, so daisyui must be present in the consuming Tailwind build (it is a peer dependency of the kit). It is built for the Waffles app: do not import it into an app that already declares its own prefersdark: true DaisyUI theme, since DaisyUI auto-applies the last such theme and waffles-dark would override it under an OS dark-mode preference.

The reviewed snapshot of every token lives in src/appearance/waffles.test.ts.

Components

All components from @playaos/ui-default are re-exported. The following receive PlayaOS brand overrides:

| Component | Override | |-----------|---------| | PlanLimitAlert | Brand accent background | | DirectoryProfileCard | Brand border, link, and badge colors | | DataTable | Brand muted header and selected row |

All other components (AdminShellLayout, DataTableColumnHeader, DataTablePagination, DataTableViewOptions, DraggableRow) are re-exported as-is from @playaos/ui-default.