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

@monowind/themes

v0.2.11

Published

Themes for monowind modeled on real systems: DOS, C64, phosphor terminals — palettes, period fonts, era-correct border glyphs

Readme

@monowind/themes

Themes for monowind modeled on real systems — authentic palette, period font, and era-correct border characters, one CSS file each:

| theme | system | font | borders | | ---------------- | -------------------------------- | ------------------------ | ----------------------------- | | dos | IBM PC text mode (VGA 16-color) | Px437 IBM VGA 8x16 | CP437 single + double | | dos-blue | the Norton/Turbo Vision look | Px437 IBM VGA 8x16 | CP437 single + double | | green-phosphor | P1 green monochrome terminal | Px437 IBM VGA 8x16 | single lines only (DEC-style) | | amber | P3 amber monochrome terminal | Px437 IBM VGA 8x16 | single lines only | | c64 | Commodore 64 | Pet Me 64 (square cells) | PETSCII-style rounded corners | | teletype | hard-copy terminal, ink on paper | Courier stack | 7-bit ascii (+-\|, +=+) | | bbs | dial-up BBS, ANSI art | Px437 IBM VGA 8x16 | CP437 blocks (, /) |

Usage

Import a theme next to monowind's stylesheet and put its class on a <mono-wind> (or any wrapper):

@import "tailwindcss";
@import "monowind";
@import "@monowind/themes/dos";

(or @import "@monowind/themes" for all of them — class scoping means unused themes cost nothing)

<mono-wind class="theme-dos">…</mono-wind>

No build? Themes are plain CSS — load one with a <link> next to the monowind CDN script (fonts and palettes resolve relative to it):

<link rel="stylesheet" href="https://unpkg.com/@monowind/themes/themes/dos.css" />

Themes are CLASS-SCOPED: two hosts on one page can wear different themes, all theme files can load at once, and no class means monowind's defaults. Everything a theme sets is overridable — utilities beat it.

The whole Tailwind palette is quantized. Each theme remaps every --color-* token to its system's colors (nearest-in-OKLAB; lightness steps for the monochromes), scoped to themed hosts: text-red-500 inside green-phosphor renders the right brightness of green, and the rest of your page keeps stock colors. Arbitrary values (text-[#f00]) bypass the mapping and stay literal.

Also set per theme: --mw-fg/--mw-bg, the ANSI-16 --mw-ansi-* tokens (SGR-colored ascii art and effect filters follow the theme), the border glyph set (--mw-border-glyphs), and the font with its native bitmap size (keep font-size at integer multiples for crisp cells).

Fonts

The PC-era themes ship "Px437 IBM VGA 8x16" from the Ultimate Oldschool PC Font Pack (© VileR, CC BY-SA 4.0 — license in fonts/LICENSES/). The c64 theme ships "Pet Me 64" from Kreative Korp's Commodore font set (© Kreative Software, Relay Fonts Free Use License — license in fonts/LICENSES/, the file unmodified as it requires): the C64's 8×8 character cell, so its cells are square.