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

@namche/namche-shadow

v0.5.0

Published

Namche Shadow Sans, Mono, and Pixel for Next.js and framework-agnostic CSS.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

jodokjodok

Keywords

namche shadownamche shadow mononamche shadow pixelnext.js fontgeist derivative

Readme

Namche Shadow fonts for npm

The package exposes Namche Shadow Sans, Namche Shadow Mono, and the five Namche Shadow Pixel variants through next/font/local.

Installation

pnpm add @namche/namche-shadow

Usage

Framework-agnostic apps can use CDN-pinned CSS without serving font binaries from the app’s own origin:

@import "@namche/namche-shadow/fonts.cdn.css";

The URLs are generated from this package’s version, so updating the package selects the matching immutable CDN release. Family-only entry points are sans.cdn.css, mono.cdn.css, pixel.cdn.css, and geist.cdn.css.

Controlled Namche properties that only need the maintained Latin web set can use fonts-latin.cdn.css, or one of sans-latin.cdn.css, mono-latin.cdn.css, pixel-latin.cdn.css, and geist-latin.cdn.css. These point to physically subsetted WOFF2 files and include matching unicode-range descriptors.

The geist entry points expose upstream Vercel Geist Sans variable faces, bundled byte for byte so Namche applications can load their Geist body font from the same package or CDN release. Next.js apps that want automatic font optimisation for Geist should keep using Vercel's own geist package.

Projects that do not need the npm dependency can import the versioned CDN stylesheet directly:

@import url("https://cdn.namche.ai/fonts/namche-shadow/v0.2.1/fonts.css");

Its internal font URLs are relative to that version root, making the stylesheet bytes reusable across release tags while each versioned import remains immutable. The current/ alias is only a preview pointer and must never be pinned in production.

For fully self-hosted deployments, import all three families from package-relative CSS:

@import "@namche/namche-shadow/fonts.css";

Or import only the families they use:

@import "@namche/namche-shadow/sans.css";
@import "@namche/namche-shadow/mono.css";
@import "@namche/namche-shadow/pixel.css";

The self-hosted Latin equivalents are fonts-latin.css, sans-latin.css, mono-latin.css, and pixel-latin.css. Use the unsuffixed entry points for user-generated or multilingual text and for Mono content that needs box drawing or technical symbols.

This path includes the WOFF2 files in the application build and works offline or in air-gapped environments.

Next.js apps should keep using the next/font/local entry points for automatic font optimisation:

import { NamcheShadowSans } from "@namche/namche-shadow/font/sans";
import { NamcheShadowMono } from "@namche/namche-shadow/font/mono";

export default function Layout({ children }) {
  return (
    <html className={`${NamcheShadowSans.variable} ${NamcheShadowMono.variable}`}>
      <body>{children}</body>
    </html>
  );
}

Latin-only Next.js entry points preserve the same named exports:

import { NamcheShadowSans } from "@namche/namche-shadow/font/sans-latin";
import { NamcheShadowMono } from "@namche/namche-shadow/font/mono-latin";

font/pixel-latin similarly exports all five Pixel variants. The subset files are generated from the full approved WOFF2 files during CI and release assembly; full desktop and webfont files remain available unchanged.

The default export and font/sans use the rounded Namche Shadow Sans variable fonts — upright and italic — with static fallbacks, and font/sans-latin serves the two variable Latin subsets. font/sans-non-variable keeps the static upright and italic files. The Thin through Black statics remain Michael's approved multi-tier RoundCorner references. The Mono exports currently provide upright styles.

Pixel variants are exported from @namche/namche-shadow/font/pixel:

  • NamcheShadowPixelSquare
  • NamcheShadowPixelGrid
  • NamcheShadowPixelCircle
  • NamcheShadowPixelTriangle
  • NamcheShadowPixelLine

The Namche Shadow Sans design direction and implementation is done by Michael Marte for Ruhm etc..

This package is adapted from Vercel's geist package. The fonts remain licensed under the SIL Open Font License 1.1; see the root AUTHORS.txt and CONTRIBUTORS.txt for full credit.