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

@rathnasgala2/theme-default

v4.2.0

Published

The default presentation theme for Galascribe portable publications (`@rathnasgala2/template@^4.4.0`). It is what a build uses when no other theme is selected. This package is a **closed, passive file set**: JSON and CSS only, no JavaScript, no build step

Vulnerabilities

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

Links

Git

Maintainers

anandrathnasanandrathnas

Keywords

Readme

@rathnasgala2/theme-default

The default presentation theme for Galascribe portable publications (@rathnasgala2/template@^4.4.0). It is what a build uses when no other theme is selected. This package is a closed, passive file set: JSON and CSS only, no JavaScript, no build step, no runtime dependency, no lifecycle script. A missing selected theme fails a build rather than silently changing appearance.

In generation 4 the template owns page layout and component structure. This theme selects the Newsletter composition and supplies its established 116-token Default palette plus a small amount of skin CSS.

Composition

theme.json embeds the complete generation-4 Newsletter composition:

  • newspaper home
  • issue article
  • profile author page
  • issue listings
  • publication header
  • expanded footer
  • landscape media
  • comfortable density

Files

  • package.json: exactly name, version, license, repository, files.
  • theme.json: validated against urn:gala:schema:theme-contract:2.0.0. It carries the contract-4 identity and Newsletter composition, templateRange (^4.4.0), the stylesheet/layer/hook projection, both palettes for all 116 tokens, asset digests, size budgets, and the generation-4 stylingContractDigest.
  • tokens.css: generated from theme.json by tokens:generate. Never edit it by hand; tokens:check fails if it drifts from theme.json.
  • components.css: a small skin layer (cards, chips, avatars, strong text) that uses tokens only.
  • print.css: print rules.
  • LICENSE, README.md.

Token values are the owner-approved Default look. theme.json is their only source: edit its tokens, then run tokens:generate and digest:generate; never edit tokens.css.

Commands

Node 24.18.0 (see .nvmrc). tooling/ is private and never packed; every gate lives in @rathnasgala2/theme-tooling and is reached through tooling/run.mjs.

npm --prefix ../theme-tooling run vendor:check
npm --prefix ../theme-tooling ci
GALA_THEME_TOOLING_DIR=../../theme-tooling npm --prefix tooling run tokens:generate
GALA_THEME_TOOLING_DIR=../../theme-tooling npm --prefix tooling run digest:generate
GALA_THEME_TOOLING_DIR=../../theme-tooling npm --prefix tooling run verify

Re-run digest:generate after editing theme.json, tokens.css, components.css or print.css. It recomputes asset digests and the chain fixtureDigest, evidenceDigest, integrity.

Only theme tooling is consumed from an explicit source checkout. Its exact Schema 3.16.0 and Template 4.4.0 dev dependencies install from the npm registry, and Schema and Template resolve from those installed packages. GALA_SCHEMA_DIR and GALA_TEMPLATE_DIR are development overrides, not part of this flow. None is a runtime dependency, and these commands do not publish the package.

Rules

CSS is limited to the root scope and the template's published styling hooks, contains no @import, external url(), outline: none or script constructs, and every stylesheet is one @layer block matching theme.json. Contrast (WCAG 2.2 AA) is checked for both palettes by contrast:check. The shared tooling README describes each gate.