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

@fresh-ds/tokens

v0.1.3

Published

`@fresh-ds/tokens` is the authority for all reusable visual values in Fresh.

Readme

@fresh-ds/tokens

@fresh-ds/tokens is the authority for all reusable visual values in Fresh.

The intended visual character is documented in docs/visual-recipe.md.

Naming Model

There are two token layers, and they should never be mixed casually:

  1. Raw tokens Use these only when defining semantic roles. Raw names are neutral building blocks such as neutral.900, accent.600, 4, md, or normal.

  2. Semantic tokens Use these everywhere else. Semantic names describe UI intent instead of color families or one-off styling choices.

Semantic Color Roles

  • canvas: app and page backgrounds
  • surface: contained UI such as cards, grouped sections, and disabled fills
  • border: separators, field outlines, strong edges, and focus treatment
  • content: text and icon foregrounds
  • action: interactive surfaces such as buttons
  • feedback: status communication for success, warning, danger, accent, and neutral
  • input: field-specific text, placeholder, border, and background roles

Rules

  • Product code should never import raw palettes to make styling decisions.
  • Component code should choose semantic intent first, then map variants to that intent.
  • If a new brand arrives later, raw token values can change without renaming semantic callers.
  • If a new component needs a visual role that does not fit the current semantic model, add a new semantic role instead of bypassing the system with inline values.