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

pequod-tailwind

v0.2.0

Published

Pequod colour palette for Tailwind CSS — warm paper, deep ink, and eight crew accents named after the crew of Moby-Dick's whaler.

Readme

pequod-tailwind

The Pequod palette for Tailwind CSS — the full Log base scale, eight crew accents (light + dark variants), all named after the crew of the whaler in Moby-Dick. Designed for long-form reading, not glance- ability.

The narrative, design rationale, and full accessibility analysis live in the main repository and on the project website.

Install

npm install pequod-tailwind
# or: pnpm add pequod-tailwind
# or: yarn add pequod-tailwind

Use — Tailwind v3

tailwind.config.js:

const pequod = require("pequod-tailwind");

module.exports = {
  content: ["./src/**/*.{html,js,ts,jsx,tsx}"],
  theme: {
    extend: {
      colors: pequod.colors,   // log + all eight crew accents
    },
  },
};

Now you can write classes like:

<body class="bg-log-50 text-log-800 dark:bg-log-950 dark:text-log-100">
  <h1 class="text-queequeg dark:text-queequeg-dark">Pequod</h1>
  <p class="text-log-700 dark:text-log-300">
    A pigment-inspired colour palette for reading and code.
  </p>
  <code class="bg-log-150 text-daggoo dark:bg-log-900 dark:text-daggoo-dark">
    palette("crew")
  </code>
  <button class="bg-starbuck text-log-50 hover:bg-starbuck-dark">
    Read on
  </button>
</body>

Use — Tailwind v4

app.css (or wherever your @theme lives):

@import "tailwindcss";
@import "pequod-tailwind/index.js" layer(theme);

/* or, more precisely, declare the tokens yourself: */
@theme {
  --color-log-50:  #F7F3EE;
  --color-log-100: #EAE1D7;
  /* ... etc; see `node_modules/pequod-tailwind/index.js` for all values */
  --color-ahab:    #A83732;
  --color-ahab-dark: #E3877C;
}

(A first-class v4 plugin is on the roadmap once Tailwind v4's plugin API stabilises further.)

Apply only what you need

If you don't want every Pequod colour to leak into your tab-completion in editors, pull just the shades you use:

const pequod = require("pequod-tailwind");

module.exports = {
  theme: {
    colors: {
      paper:  pequod.log[50],
      ink:    pequod.log[950],
      muted:  pequod.log[600],
      accent: pequod.crew.starbuck.DEFAULT,
      danger: pequod.crew.ahab.DEFAULT,
    },
  },
};

API

const pequod = require("pequod-tailwind");

pequod.log        // { 50: "#F7F3EE", 100: "#EAE1D7", ..., 950: "#0B1720" }
pequod.crew       // { ahab: { DEFAULT, light, dark }, starbuck: {...}, ... }
pequod.colors     // { log, ahab, starbuck, queequeg, pip, ishmael,
                  //   stubb, tashtego, daggoo }

Every crew member has a DEFAULT (so bg-ahab works) plus an explicit light and dark. The defaults are the saturated "light-mode" variants — designed against Log 100 paper. Dark-mode variants are tuned for Log 950 ink and clear WCAG-AA on that surface.

Accessibility

  • Body-text contrast on the light theme: 10.5 : 1 (Log 800 on Log 50). On dark: 16.2 : 1 (Log 100 on Log 950).
  • All eight dark-mode crew accents clear WCAG-AA (4.5 : 1) on Log 950.
  • Five of eight light-mode crew accents clear AA-body on Log 100; the other three (Pip, Stubb, Starbuck) sit between 3.3 and 4.1 — fine for bold, large text, or UI elements where AA-large (3 : 1) applies.

The full colour-vision-deficiency analysis (including which crew pairs collapse under each dichromacy) lives in the main repository.

Beyond Tailwind

Pequod also ships as:

  • VS Code themes (Marketplace + Open VSX) — tiagojct.pequod-color-theme
  • Zed theme family (dark + light, single file)
  • iTerm2 / Ghostty / Alacritty / kitty / WezTerm / tmux / Windows Terminal — terminal presets
  • Python package — pip install pequod
  • R package — install from GitHub or CRAN (review pending)
  • Printable A4 specimen PDF generated from the canonical tokens

All of these live at github.com/tiagojct/pequod.

Licence

MIT. The underlying palette tokens are also published under CC-BY-4.0 in the upstream repository.