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

@qdesignsystems/able-ui

v0.1.0

Published

Able Design System UI primitives — same components as Able Studio gallery (for Lovable and external React apps).

Readme

@qdesignsystems/able-ui

Publishable UI primitives from Able Studio — the same components/ui sources used in /studio/preview/{clientId}.

Where this package lives

able-design-system/              ← git repo root (Studio app)
├── components/ui/               # source of truth — author here
├── packages/able-ui/            ← this package (@qdesignsystems/able-ui)
│   └── src/                     # generated by npm run able-ui:sync
└── scripts/sync-able-ui-package.ts

Studio remains where you author components. This package is the distribution artifact for Lovable and other React apps.

Sync from Studio

npm run able-ui:sync

Copies every path in lib/studio/able-ui-package-paths.ts into packages/able-ui/src/.

Install (Lovable / Vite / React)

npm install @qdesignsystems/[email protected]

Peer dependencies (@base-ui/react, clsx, tailwind-merge, etc.) must be installed in the consumer app. See package.json peerDependencies.

import { Button } from "@qdesignsystems/able-ui/button"
import { PromptBox } from "@qdesignsystems/able-ui/prompt-box"

Configure path alias in the consumer (Vite example):

resolve: {
  alias: { "@": path.resolve("node_modules/@qdesignsystems/able-ui/src") },
}

Or import subpaths directly without @/ if you copy components.json aliases.

Brand tokens

This package ships components only. Per-client colors, radius, and fonts come from:

  • Able MCP get_brand_packtokens.css, or
  • npm run brand:export -- --client <id>

Merge tokens.css onto :root and .dark in the consumer app. Use MCP for get_component_spec / get_pattern_spec when composing screens.

Publish

  1. Change components in able-design-system/components/ui/
  2. cd able-design-system && npm run able-ui:sync
  3. Bump packages/able-ui/package.json version
  4. npm publish from packages/able-ui (requires @qdesignsystems npm org access)

Rules for 1:1 Studio parity

  • Do not hand-edit files under packages/able-ui/src/ — run sync instead.
  • Do not use npx shadcn add in consumer apps.
  • Do bump this package when Studio components change.
  • Do use Able MCP to validate fullClasses and patterns.