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

@kofile/gds-wc

v1.4.15

Published

Framework‑agnostic Web Components for the GovOS design system, built with [Lit](https://lit.dev) and powered by the same token pipeline as our React components.

Readme

@govos/wc

Framework‑agnostic Web Components for the GovOS design system, built with Lit and powered by the same token pipeline as our React components.

  • Custom elements are prefixed with neumo- (for example, <neumo-button>, <neumo-checkbox>).
  • Internal components use neumo-*-internal (e.g., <neumo-checkbox-internal>, <neumo-label>).
  • Composed components combine internal atoms (e.g., neumo-checkbox = neumo-checkbox-internal + neumo-label).
  • All styling flows through design tokens and a 3‑tier token system.
  • Components are multi‑theme by design: swapping theme stylesheets (or data-theme) updates the look without changing component code.

For a detailed look at file layout, naming, tokens, events, and a11y expectations, see ARCHITECTURE.md.

Installing

npm install @govos/wc
# or
yarn add @govos/wc

Usage

In your application:

import "@govos/wc";
// Then use <neumo-*> tags in your HTML/templates

In your HTML:

<link rel="stylesheet" href="/node_modules/@govos/wc/styles/theme-quiet.css" />

<neumo-button data-variant="primary">Save changes</neumo-button>
<neumo-checkbox checked label="Accept terms"></neumo-checkbox>

To switch themes, swap the theme stylesheet or change data-theme on the root element (see ARCHITECTURE.md §5–6).

Contributing

Required Reading

Before creating or modifying a component, you MUST read:

  1. ARCHITECTURE.md - Complete architecture documentation covering:

    • Component anatomy and naming conventions
    • Token usage and theming (3-tier token system)
    • Event patterns (neumo-* prefix)
    • Accessibility and testing expectations
    • Shadow DOM and styling strategy
  2. CONTRIBUTING.md - Development workflow and requirements:

    • Required icon library (Phosphor only)
    • Required token pipeline (MCP → Anova → foundations)
    • Required tests for each component
    • Storybook requirements
    • Internal vs. public component rules

Using Cursor AI

If you're using Cursor, automated guardrails are enforced via .cursor/rules.json:

  • Enforces Lit + LitElement base
  • Requires neumo-* event prefixes
  • Prevents raw hex values (must use tokens)
  • Enforces Phosphor icons only
  • Requires ARIA attributes for interactive components
  • Requires story + test file generation
  • Requires export in index file

See CONTRIBUTING.md for details.

File Structure

  • Component implementations: packages/wc/src/components/{name}/{name}.ts
  • Tests (colocated): packages/wc/src/components/{name}/{name}.spec.ts
  • Stories: packages/wc/stories/{name}.stories.ts
  • Shared foundations: packages/wc/src/foundations/ (base-element, events, a11y, icons, tokens)
  • Theme stylesheets: packages/wc/styles/themes/

Quick Checklist

  • [ ] Read ARCHITECTURE.md
  • [ ] Read CONTRIBUTING.md
  • [ ] Use LitElement or extend NeumoBaseElement
  • [ ] Use tokens only (no raw hex values)
  • [ ] Use Phosphor icons only
  • [ ] Use neumo-* event prefixes
  • [ ] Include ARIA attributes for interactive components
  • [ ] Create colocated test file
  • [ ] Create Storybook story
  • [ ] Export public components from src/index.ts