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

@rdna/monolith

v0.2.0

Published

MONOLITH theme package for RDNA and RadOS campaign skins

Readme

@rdna/monolith

MONOLITH theme package for RDNA campaign skins.

This MVP package provides theme-scoped CSS token overrides and lightweight
CRT/glow utilities. Follow-up work should port the remaining licensed fonts,
campaign assets, icons, and reusable components from the private campaign
source materials when that migration is explicitly scheduled.

Package status: public npm package. It is a current campaign theme surface for external RDNA consumers, including standalone RadOS, but it should still be treated as a campaign theme implementation rather than a permanent one-off theme API.

Load it after Radiants so its theme-scoped tokens can override the base
semantic values:

@import '@rdna/radiants';
@import '@rdna/monolith';

Usage

<html data-theme="monolith">
  <body>...</body>
</html>

The CSS also contains current [data-theme='skr'] selectors for the SKR campaign surface used by external consumers. The package has no React entrypoints.

Public API

| Subpath | Provides | | ------------------------ | ---------------------------------------------------------------------------- | | @rdna/monolith | Theme entrypoint that imports tokens and effects. | | @rdna/monolith/tokens | MONOLITH semantic token overrides, including light-mode overrides. | | @rdna/monolith/fonts | Placeholder font layer; the package currently inherits Radiants font tokens. | | @rdna/monolith/effects | Theme-scoped wallpaper, portal, door, logo, and CRT/glow effects. |

Architecture

tokens.css scopes semantic values to [data-theme='monolith'] and
[data-theme='monolith'].light. effects.css contains the theme-specific
wallpaper and visual-effect selectors for MONOLITH and SKR campaign states.
index.css imports the token and effects layers.

MONOLITH should be treated as a current campaign theme implementation, not as a
permanent one-off package shape. The future theme contract may move it under a
theme family layout such as packages/themes/monolith, rename it into an
@rdna/theme-* package family, or fold it into an @rdna/themes package with
theme subpath exports. Radiants should be one theme in that family, not the only
theme namespace.

Development

This package has no build or test script because it is currently a CSS-only theme surface. Validate changes through the root gate:

pnpm build

Standalone RadOS imports this package from https://github.com/Radiants-DAO/RadOS as an external consumer. Deleting or moving the package is a product/package strategy decision and should account for future themes beyond MONOLITH.