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

@resq-systems/constants

v0.7.0

Published

Shared, zero-dependency constants for ResQ Systems apps: design tokens (oklch + email-safe hex), brand identity, and cross-app values

Readme

@resq-systems/constants

Shared, zero-dependency constants for ResQ Systems apps — one source of truth reused across the marketing site, dashboard, and transactional email.

Install

bun add @resq-systems/constants

Subpaths

| Import | Contents | | --- | --- | | @resq-systems/constants | everything below | | @resq-systems/constants/tokens | colors (oklch source + email-safe hex snapshot, incl. info/success/warning/danger status roles), fonts (stacks + webfont href), radii, themeColor (light/dark PWA + viewport theme-color), plus the color-role types ColorRole, StatusRole, OklchColorRole, ColorTokenName | | @resq-systems/constants/brand | brand — name, product name, email descriptor, legal name, tagline, description, domains, email addresses, legal URLs, socials, company info, logo, postal address | | @resq-systems/constants/tokens.css | Stylesheet mirroring ./tokens: the oklch color roles, --resq-chart-1..5 palette, --resq-radius-*, and --resq-font-* stacks as CSS custom properties on :root. @import it directly. |

Everything is as const, so values are literal-typed and tree-shakeable.

Usage

import { colors, fonts } from "@resq-systems/constants/tokens";
import { brand } from "@resq-systems/constants/brand";

element.style.background = colors.hex.background; // "#0A0E1A"
const from = brand.email.from; // "ResQ Systems <[email protected]>"
const emailDescriptor = brand.emailDescriptor; // "Autonomous Disaster Response"

brand.emailDescriptor is the short descriptor beneath the company name in the shared email lockup. It does not replace brand.productName or the longer brand.tagline.

@resq-systems/email-templates sources email identity, fonts, primary and dark shell colors, and status colors from this package. Its public email contract owns the remaining email-specific light shell colors and presentation values.

Adding constants

Group by domain in its own module (src/<domain>.ts), export as const, and add a subpath in package.json exports. Keep it curated — constants earn their place by being reused across apps, not by being convenient to dump here.

Rules

  • Zero runtime dependencies. This package must stay dependency-free.
  • Values are data only — no logic; the JS is side-effect-free. Only the stylesheet (tokens.css) is a side-effectful import, declared via sideEffects.
  • A change here ripples to every dependent; prefer additive, stable edits.

Prerequisites

  • Runtime: Bun 1.1+ or Node.js 20+
  • Module format: ESM only ("type": "module"); every value is a plain as const object.

Consuming in CSS

Import the ready-made stylesheet — it declares the oklch color roles, the --resq-chart-1..5 palette, --resq-radius-*, and --resq-font-* stacks as CSS custom properties on :root:

@import "@resq-systems/constants/tokens.css";

.panel {
  background: var(--resq-color-surface);
  border: 1px solid var(--resq-color-border);
  border-radius: var(--resq-radius-lg);
  font-family: var(--resq-font-body);
}

The stylesheet mirrors ./tokens (a test fails if the two drift). For Tailwind v4, alias these custom properties inside your @theme block so utilities resolve against the same source of truth. If you need the raw values in TypeScript — or the email-safe hex snapshot — import the objects from ./tokens instead.

Testing

bun --filter @resq-systems/constants test

Troubleshooting

  • Cannot find module '@resq-systems/constants/tokens.css': There is no CSS export. Import the token objects from @resq-systems/constants/tokens and emit variables yourself.
  • Colors look wrong in email or older targets: use the email-safe colors.hex.* values, not the oklch source — many mail clients drop oklch().