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

@omnidraw/service-theme

v0.5.0

Published

Isolated theme capability, built-in themes, tokens, and DOM helpers for Omnidraw hosts.

Readme

@omnidraw/service-theme

Public theme definitions, tokens, style helpers, DOM projection helpers, and an isolated theme-service capability for Omnidraw hosts.

Every registration is one complete definition: detailed UI and interaction roles, the six role-aware canvas colors, viewport and editor affordances, and terminal colors. A registration may instead explicitly extend an existing theme. Unknown theme IDs and unknown inheritance bases throw; they never silently borrow the Light canvas palette.

Service capability

Depend on IThemeService at composition boundaries. ThemeService is the default implementation:

import {
  ThemeService,
  txApplyThemeToElement,
  type IThemeService,
} from "@omnidraw/service-theme";

const theme: IThemeService = new ThemeService();
const release = theme.subscribeThemeChange((definition) => {
  txApplyThemeToElement(canvasHost, definition);
});

txApplyThemeToElement(canvasHost, theme.getTheme());
// Later: release();

Apply variables to the host element that owns the themed UI. Importing this package never changes the document root or installs global styles.

Import @omnidraw/service-theme/default.css for generated document defaults or @omnidraw/service-theme/canvas-default.css for package-scoped canvas defaults. Both files are generated from the Light definition during the package build; runtime DOM application still uses one immutable ThemeService snapshot.

Each ThemeService owns its registry, active selection, listeners, and remembered styles. Creating or changing one instance does not mutate another. The remembered-style API remains a host capability; it does not replace the canvas editor's selection-style authority.

Release verification

bun run typecheck
bun run test
bun run build

The published package contains built ESM, declarations, and generated CSS under dist/. Its only runtime dependency is the state-free @omnidraw/theme-contract package.