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

@bootnodedev/canton-theme

v0.4.0

Published

Plain-CSS theme for @bootnodedev/canton-dappbooster

Vulnerabilities

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

Links

Git

Maintainers

pablofullanapablofullanaluchobonatti.bnluchobonatti.bngabitoesmiapodogabitoesmiapodofernandomgfernandomglmcorbalanlmcorbalannico_bnnico_bnfzavaliafzavalia

Keywords

Readme

@bootnodedev/canton-theme

Plain-CSS theme (L3) for @bootnodedev/canton-dappbooster components. Zero JavaScript, zero runtime. Two consumable artifacts:

| Export | What it is | | --- | --- | | @bootnodedev/canton-theme/tokens.css | --cnc-* custom properties — the theming + dark-mode contract | | @bootnodedev/canton-theme/default.css | prestyled defaults selecting on component part classes; imports tokens.css |

Usage

Components ship no styling; import the theme once at your app entry:

import '@bootnodedev/canton-theme/default.css'
  • default.css imports tokens.css, so that one line is the whole theme. Import tokens.css alone to take the contract without the prestyled defaults. Defining the --cnc-* properties yourself instead means setting color-scheme directly, one explicit value per mode: it is not a --cnc-* property, so skipping it leaves the browser painting scrollbars, form controls, and the caret in the wrong mode.
  • Dark mode activates on [data-theme="dark"]. Set that attribute on <html>, as early as you can: applied after first paint it flashes. It deliberately does not follow prefers-color-scheme by itself, so that a mode toggle can override the OS preference in both directions. canton-dappbooster's <ThemeProvider> drives it from React; nothing here depends on that, and setting the attribute yourself is equally valid.
  • Overriding a token means overriding it in both modes. Your :root also beats our [data-theme="dark"] block, so a light-only override stays applied in dark.
  • The whole package lives under @layer cnc, so any unlayered CSS of yours wins without specificity fights, whether you import us first or last.

With Tailwind, position the cnc layer explicitly. Tailwind otherwise owns the layer order it emits, and its preflight resets button { color: inherit }, which beats the theme's copy-control colours. Declare the order yourself, before the first @import:

@layer properties, theme, base, cnc, components, utilities;

@import "tailwindcss";

Any layer Tailwind emits that the statement omits lands on top of the ones it names, so keep properties (its @property polyfill) in the list.

Why a separate package

Components (L2) carry zero styling opinion; the theme (L3) is a separate concern styling the DOM contract each component declares in its anatomy.ts. See ../canton-dappbooster/architecture.md.