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/react

v1.0.1

Published

React components for Domternal editor

Downloads

1,022

Readme

@domternal/react

Version MIT License

React components and hooks for the Domternal editor. Wraps the headless @domternal/core editor with React-native APIs: a composable Domternal component with namespaced subcomponents, a useEditor hook for full control, an EditorProvider context, and ReactNodeViewRenderer for writing custom node views as React components. Works with React 18 and React 19.

Links

Website    •    Documentation    •    Live examples

Install

pnpm add @domternal/react @domternal/core @domternal/theme react react-dom

react (>=18), react-dom (>=18), and @domternal/core (>=1.0.0) are peer dependencies. Import the theme (@domternal/theme) in your entry CSS for default styling:

@import '@domternal/theme';

Usage

The recommended pattern uses the composable Domternal component. It creates the editor and provides it to every subcomponent via context, so no editor prop needs to be passed down:

import { Domternal } from '@domternal/react';
import { StarterKit, BubbleMenu } from '@domternal/core';

export default function Editor() {
  return (
    <Domternal
      extensions={[StarterKit, BubbleMenu]}
      content="<p>Hello from React!</p>"
    >
      <Domternal.Toolbar />
      <Domternal.Content />
      <Domternal.BubbleMenu contexts={{ text: ['bold', 'italic', 'underline'] }} />
    </Domternal>
  );
}

Need direct access to the editor instance? Use the useEditor hook and mount the view yourself:

import { useEditor, EditorProvider, DomternalToolbar } from '@domternal/react';
import { StarterKit } from '@domternal/core';

export default function Editor() {
  const { editor, editorRef } = useEditor({
    extensions: [StarterKit],
    content: '<p>Hello</p>',
    onUpdate: ({ editor }) => console.log(editor.getHTML()),
  });

  return (
    <EditorProvider editor={editor}>
      {editor && <DomternalToolbar />}
      <div className="dm-editor">
        <div ref={editorRef} />
      </div>
    </EditorProvider>
  );
}

Options

useEditor(options, deps?) and <Domternal> take the same options:

| Option | Type | Default | Description | |---|---|---|---| | extensions | AnyExtension[] | [] | Extensions to load on top of DEFAULT_EXTENSIONS. | | history | boolean | true | Whether the built-in History extension is loaded. Turn it off when an extension brings its own undo. | | content | Content | '' | Initial content, HTML string or JSON. Changing it syncs the editor. | | editable | boolean | true | Whether the editor is editable. | | preset | 'classic' \| 'notion' | 'classic' | 'notion' paints dm-notion-mode on the .dm-editor host and switches preset-aware extensions to their Notion behavior. Create-time only. | | autofocus | FocusPosition | false | Where to place the caret on mount. | | outputFormat | 'html' \| 'json' | 'html' | Format used when comparing the content prop against the document. | | immediatelyRender | boolean | false | Create the editor during the first render, so editor is never null. Throws in SSR. |

onCreate, onUpdate, onSelectionChange, onFocus, onBlur, and onDestroy callbacks are accepted alongside them. <Domternal> additionally takes deps, the dependency array useEditor reads as its second argument: change a value in it and the editor is rebuilt.

Exports

  • Hooks: useEditor, useEditorState (full state or a granular selector), useCurrentEditor, useNotionColorPicker
  • Constants: DEFAULT_EXTENSIONS
  • Composable component: Domternal with Domternal.Toolbar, Domternal.Content, Domternal.BubbleMenu, Domternal.FloatingMenu, Domternal.EmojiPicker, Domternal.Loading
  • Components: DomternalEditor, EditorContent, DomternalToolbar, DomternalBubbleMenu, DomternalFloatingMenu, DomternalEmojiPicker, DomternalNotionColorPicker, EditorProvider
  • Node views: ReactNodeViewRenderer, NodeViewWrapper, NodeViewContent, useReactNodeView
  • Core re-exports: the Editor class plus the Content, AnyExtension, FocusPosition, and JSONContent types
  • SSR helpers (re-exported from core, work without an editor instance): generateHTML, generateJSON, generateText