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

@editora/themes

v1.0.12

Published

Themes and styling system for Editora Rich Text Editor with light/dark mode support

Readme

@editora/themes

[!IMPORTANT] Live Website: https://editora-ecosystem.netlify.app/
Storybook: https://editora-ecosystem-storybook.netlify.app/

Themes and design tokens for Editora editor UIs (React wrapper + Web Component).

Installation

npm install @editora/themes

Built-in Themes

  • default (@editora/themes/themes/default.css)
  • dark (@editora/themes/themes/dark.css)
  • acme (@editora/themes/themes/acme.css)

Quick Start

React

import { EditoraEditor } from "@editora/react";
import { BoldPlugin, ItalicPlugin } from "@editora/plugins";

import "@editora/themes/themes/default.css";
import "@editora/themes/themes/acme.css";

export default function App() {
  return (
    <div data-theme="acme">
      <EditoraEditor plugins={[BoldPlugin(), ItalicPlugin()]} />
    </div>
  );
}

Use data-theme="light", data-theme="dark", or data-theme="acme" on a wrapper.

Web Component

<link rel="stylesheet" href="/node_modules/@editora/core/dist/webcomponent.min.css" />
<link rel="stylesheet" href="/node_modules/@editora/themes/themes/acme.css" />
<script type="module" src="/node_modules/@editora/core/dist/webcomponent.js"></script>

<editora-editor
  theme="acme"
  plugins="bold italic underline history"
  toolbar-items="undo redo | bold italic underline"
  height="320"
></editora-editor>

Use theme="light", theme="dark", or theme="acme" on <editora-editor>.

Create A Custom Theme From Scratch

1) Start from base theme

Create my-theme.css and load default.css first:

@import "@editora/themes/themes/default.css";

2) Scope your theme

Choose one scope that works for both React and Web Component:

:is([data-theme="my-brand"], .editora-theme-my-brand) {
  /* tokens */
}

3) Override design tokens

Use the real token names used by Editora (--rte-*):

:is([data-theme="my-brand"], .editora-theme-my-brand) {
  --rte-color-primary: #1d4ed8;
  --rte-color-primary-hover: #1e40af;
  --rte-color-text-primary: #0f172a;
  --rte-color-text-secondary: #334155;
  --rte-color-text-muted: #64748b;
  --rte-color-bg-primary: #ffffff;
  --rte-color-bg-secondary: #f8fafc;
  --rte-color-bg-tertiary: #e2e8f0;
  --rte-color-border: #cbd5e1;
  --rte-color-border-light: #dbe3ee;
  --rte-color-border-focus: #1d4ed8;
  --rte-shadow: 0 6px 16px rgba(15, 23, 42, 0.1);
  --rte-shadow-lg: 0 16px 28px rgba(15, 23, 42, 0.16);
}

4) Add component overrides

Tokens handle most styling, but buttons/dropdowns/content usually need explicit overrides:

:is([data-theme="my-brand"], .editora-theme-my-brand) :is(.rte-toolbar, .editora-toolbar) {
  background: #f4f8ff;
  border-color: var(--rte-color-border);
}

:is([data-theme="my-brand"], .editora-theme-my-brand) :is(.rte-toolbar-button, .editora-toolbar-button) {
  background: #ffffff;
  border-color: var(--rte-color-border);
  color: var(--rte-color-text-secondary);
}

:is([data-theme="my-brand"], .editora-theme-my-brand) :is(.rte-content, .editora-content) {
  background: #ffffff;
  color: var(--rte-color-text-primary);
}

5) Load and activate the theme

  • React: import CSS + set wrapper data-theme="my-brand".
  • Web Component: include CSS + set theme="my-brand" on <editora-editor>.

Modify An Existing Theme

Option A: Extend dark theme

@import "@editora/themes/themes/default.css";
@import "@editora/themes/themes/dark.css";

:is([data-theme="dark"], .editora-theme-dark) {
  --rte-color-primary: #22d3ee;
  --rte-color-primary-hover: #06b6d4;
}

:is([data-theme="dark"], .editora-theme-dark) .rte-toolbar-button {
  border-radius: 8px;
}

Option B: Extend acme theme

@import "@editora/themes/themes/default.css";
@import "@editora/themes/themes/acme.css";

:is([data-theme="acme"], .editora-theme-acme) {
  --rte-color-primary: #7c3aed;
  --rte-color-primary-hover: #6d28d9;
}

Safe override strategy

  1. Keep selectors scoped ([data-theme="..."] / .editora-theme-...).
  2. Prefer token overrides first, component selectors second.
  3. Override both React and Web Component class names where needed:
    • React classes: .rte-*
    • Web Component classes: .editora-*

New acme Theme Notes

acme.css is intentionally shared across both renderers:

  • React support via [data-theme="acme"]
  • Web Component support via .editora-theme-acme (set automatically from theme="acme")

Verification Checklist

After adding/changing a theme, verify:

  1. Toolbar buttons (normal/hover/active/disabled)
  2. Dropdown menus and inputs (including font-size input placeholder)
  3. Editor content colors + placeholder visibility
  4. Status bar + floating toolbar
  5. Dialogs and plugin overlays in both light/dark/custom scopes
  6. Multi-instance behavior with different themes on the same page

License

MIT