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

@addaab/ads

v0.3.0

Published

Adda Design System — tokens, web components, React wrappers, and CSS. AI agents: read AGENTS.md (setup + rules), docs/components.md (component API) and docs/tokens.md (design tokens).

Readme

Adda Design System (@addaab/ads)

Design tokens, Stencil web components, generated React wrappers, and CSS — shipped as one installable package.

For AI agents (Claude Code, Claude Design, Lovable, v0, Cursor …)

Read these before generating code with this package (they ship inside it):

  • AGENTS.md: required setup (CSS, Avenir Next font), React patterns, server-rendered pages (markup contract), component catalogue, host page CSS and rules
  • docs/components.md: every component's props, events, slots, and HTML and React examples
  • docs/tokens.md: design tokens and which ones to use
  • llms.txt: index of the above; docs/custom-elements.json is the Custom Elements Manifest

Install

npm install @addaab/ads

For the React wrappers, also install their peer dependencies:

npm install @stencil/react-output-target react react-dom

Prefixes

| Kind | Convention | Example | |------|------------|---------| | Custom elements | ads- tag | <ads-button> | | CSS classes | ads- BEM | .ads-button, .ads-button--primary | | Token CSS variables | Figma export names (unchanged) | --component-color-…, --alias-… |

Consumption modes

1. Vite + custom elements (preferred)

Tree-shakeable: import only what you use, then register that element.

import { defineCustomElement } from '@addaab/ads/components/ads-button';
import '@addaab/ads/css'; // or `@addaab/ads/css/ads-button` + `@addaab/ads/tokens/css`

defineCustomElement();
<ads-button variant="primary">Open account</ads-button>

React wrappers call defineCustomElement for you.

2. React (generated wrappers)

React bindings are produced by @stencil/react-output-target during the Stencil build. Do not hand-maintain them.

import { AdsButton } from '@addaab/ads/react';
import '@addaab/ads/css';

<AdsButton variant="primary">Open account</AdsButton>

Per-component: import { AdsButton } from '@addaab/ads/react/ads-button'.

3. CSS only (vanilla HTML)

<button class="ads-button ads-button--primary ads-button--medium" type="button">Open account</button>
import '@addaab/ads/css/ads-button';
import '@addaab/ads/tokens/css';

4. Lazy loader (no bundler)

import { defineCustomElements } from '@addaab/ads/loader';
defineCustomElements();

Prefer mode 1 with Vite.

Package exports

| Import | Purpose | |--------|---------| | @addaab/ads/components/<name> | Custom element module (auto-defines) | | @addaab/ads/react | Generated React wrappers | | @addaab/ads/css | Tokens + all component CSS | | @addaab/ads/css/<name> | Single component CSS | | @addaab/ads/tokens | Token JSON | | @addaab/ads/tokens/css | Token CSS variables | | @addaab/ads/tokens/typography | .ads-type-* typography classes (included in @addaab/ads/css) | | @addaab/ads/tokens/js | Token list as JS (tokens array: path, CSS variable, value) | | @addaab/ads/AGENTS.md | Consumer guide for AI agents and developers | | @addaab/ads/docs/* | Generated API reference (components.md, tokens.md, custom-elements.json) | | @addaab/ads/loader | Stencil lazy loader |

Light DOM policy

Components use light DOM by default (shadow: false) for SEO and accessibility. Use shadow DOM only when a component needs strong isolation; that component's readme documents the reason.

Source & contributing

Source, issue tracking, and contribution docs live in the Adda Design System Azure DevOps repo (packages/ads). See docs/RELEASING.md there for how releases are cut.