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

@excom/valence

v0.1.3

Published

Semantic CSS with class / ARIA aliases for native HTML and custom elements

Readme

Valence.css

Classless CSS that still loves your custom elements — Pico's elegance, remixed for the modern web.

Valence.css is a lightly modified fork of the excellent Pico CSS. Pico styles are tightly bound to native tag names (article, button, …), which custom elements cannot reuse. Valence.css keeps Pico's look and adds:

  • Tag aliases — @custom-selector synonyms so [role="…"] / .tag-* (and custom element tags) share the same semantic styles
  • Opt-outs — .unstyled / .unstyled-all (and .unanimated*) for document flexibility where framework styles would fight you
  • Drop-in themes — basic (Pico-faithful) ships today; further themes share the same tokens so they can be swapped without touching markup. Light/dark is a scheme ([data-scheme])
  • Molecules — cards, dropdowns, modals (dialog::backdrop / [role="presentation"] / .tag-backdrop), nav, progress, and native [popover] styles on top of Pico's element styles
  • Tokens — --pico-* renamed to --v-* for a clear Valence.css namespace

Features

  • Semantic tag aliases Style article, dialog, button, … — the same rules apply to the [role="…"] / .tag-* forms
  • Custom-element friendly class="tag-article" on any host inherits Valence.css styles without rewriting selectors
  • Drop-in themes basic (Pico-flavor) ships; further themes share the same tokens. Scheme via [data-scheme="light|dark"]
  • Opt-outs .unstyled / .unstyled-all (and motion: .unanimated*)
  • Molecules Cards, dropdowns, modals (dialog::backdrop / [role="presentation"] / .tag-backdrop), nav, progress, popovers, tooltips

Installation

Usage

Import a theme entry (CSS). Prefer aliases when styling custom elements.

@import "@excom/valence/basic.css";
<article>Native card</article>
<event-handler class="tag-article">Aliased card</event-handler>
<button class="outline secondary">Outline</button>

Documentation

Getting started

  • Color schemes — automatic light / dark, data-scheme
  • Aliases — tag, role and .tag-* forms of every alias; custom elements
  • Opt-outs — .unstyled, .unanimated, .abstract

Customization

Layout

Content

Forms

Components

API Reference


Full documentation: https://nucleus.excom.dev/packages/valence