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

@domternal/theme

v1.0.1

Published

Default themes and styles for Domternal editor

Readme

@domternal/theme

Version MIT License

Ready-made light and dark styles for the Domternal editor, toolbar, bubble menu, floating menu, popovers, and every UI component. It is a CSS-only package (no JavaScript), built from Sass and shipped as a single compiled stylesheet. Every visual property is exposed as a CSS custom property, so you can rebrand colors, fonts, spacing, and borders by overriding a variable instead of touching the source. It also carries the paper layer: printing an editor produces the document rather than the screen, with the toolbar, menus, popovers, and hover affordances hidden, and that applies to the reader's own Ctrl/Cmd+P without any JavaScript. Colour is the one thing printing takes back: the whole light palette is re-emitted on .dm-editor with !important, so a dark document, and a custom palette with it, prints light. Hiding the host application's own chrome around the editor is the one part that takes code: that layer is gated behind the dm-printing class, which the Print extension in @domternal/core sets.

Links

Website    •    Documentation    •    Live examples

Install

pnpm add @domternal/theme

This package has no peer dependencies.

Usage

Import the stylesheet once in your application entry point:

// JavaScript/TypeScript bundler (Vite, Webpack, esbuild)
import '@domternal/theme';
// Sass pipeline (imports the SCSS source)
@use '@domternal/theme/scss';
<!-- Plain HTML link tag -->
<link rel="stylesheet" href="node_modules/@domternal/theme/dist/domternal-theme.css" />

Light mode is the default. Toggle dark mode by adding a class to the editor or any ancestor element:

<!-- Always dark -->
<div class="dm-theme-dark">
  <div class="dm-toolbar">...</div>
  <div class="dm-editor">...</div>
</div>

<!-- Follow the system preference -->
<div class="dm-theme-auto">...</div>

<!-- Force light inside a dark context -->
<div class="dm-theme-light">...</div>

For a Notion-style look (borderless surface, centered narrow column), create the editor with preset: 'notion', which paints the dm-notion-mode class on the .dm-editor host for you; adding the class by hand still works and is what the preset does. The reading measure is --dm-notion-column-width (default 44rem) and sits on the content column, so the host itself stays full width. See the theming guide for details.

Override any CSS custom property to customize the look, on screen. Print normalises the colour tokens (see the paper layer above); to keep a colour of your own on the page, redeclare it !important in your own @media print block loaded after this package. The defaults are declared on .dm-editor and .dm-toolbar themselves, and a declaration on the element beats one inherited from an ancestor, so target those elements rather than a wrapper alone:

/* Tokens the toolbar reads too */
.my-app .dm-editor,
.my-app .dm-toolbar {
  --dm-accent: #e11d48;
  --dm-accent-hover: #be123c;
  --dm-accent-surface: rgba(225, 29, 72, 0.1);
}

/* Editor-only tokens */
.my-app .dm-editor {
  --dm-editor-bg: #fefce8;
}

The hidden attribute

hidden works on every element this theme styles, and on anything inside one:

toolbar.hidden = true;   // the toolbar is gone, not merely emptied

Worth stating because it is not free. [hidden] { display: none } comes from the user agent stylesheet, and author styles beat the user agent stylesheet whatever their specificity, so any component rule that sets display disables the attribute for that element. .dm-toolbar sets display: flex, so a hidden toolbar used to leave an empty strip with the toolbar's background, border and padding, and nothing in the console. One scoped rule restores it for the whole theme.

hidden="until-found" is deliberately left alone: it does not mean display: none, it means the element stays findable and the browser reveals it when find-in-page lands inside.

Entry points

| Import | Resolves to | Description | |---|---|---| | @domternal/theme | dist/domternal-theme.css | Default: compiled CSS | | @domternal/theme/css | dist/domternal-theme.css | Explicit CSS import | | @domternal/theme/scss | src/index.scss | SCSS source for Sass pipelines |