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

@alternatefutures/tokens

v0.2.0

Published

AlternateFutures design tokens — Tailwind v4 @theme CSS variables (oklch brand system, brand accent #A5B2FF) + framework-agnostic JS color helpers. The single source of truth for the brand.

Downloads

22

Readme

@alternatefutures/tokens

The single source of truth for the AlternateFutures brand: a Tailwind v4 CSS-first @theme token system (oklch dark terminal palette, radius scale, brand accent #A5B2FF) plus framework-agnostic JS color helpers.

Install

npm install @alternatefutures/tokens

Usage

Full brand chrome (instant match)

In your app's global stylesheet:

@import "tailwindcss";
@import "@alternatefutures/tokens/theme.css";

This gives you the tokens and the opinionated base layer: monospace body font, the ambient brand glow, the CRT scanline overlay, and the .af-scroll brand scrollbar utility.

Tokens only (variables, no global chrome)

@import "tailwindcss";
@import "@alternatefutures/tokens/tokens.css";

You then get the brand colors as Tailwind utilities — bg-background, text-foreground, bg-primary, text-term, border-term-faint, rounded-lg, etc. — without the body font / ambient effects.

JS color helpers

import { BRAND, AVATAR_COLORS, seedColor } from "@alternatefutures/tokens";

const accent = BRAND.term;           // "#a5b2ff"
const color = seedColor(fingerprint); // stable per-identity oklch color

Use these where CSS variables can't reach (canvas, charts, inline styles, server-computed colors).

What's in here

  • tokens.css:root/.dark CSS variables + Tailwind v4 @theme inline map. Values only.
  • theme.css@import "./tokens.css" + the base layer (body font, glow, CRT, scrollbar).
  • dist/ — JS exports (BRAND, AVATAR_COLORS, seedColor), ESM + CJS + types.

Conventions

This package is values + brand chrome only — no React, no components. Shared React primitives belong in @alternatefutures/ui; product-specific components in @alternatefutures/<product>-ui. To change a token: edit the CSS (and the JS mirror if relevant), add a changeset (adding a token = minor; renaming/removing = major via deprecate → alias → remove), and let CI version + publish.