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

v1.8.0

Published

ProseMirror package re-exports for Domternal

Readme

@domternal/pm

Version MIT License

Shared ProseMirror dependencies for Domternal. Each @domternal/pm/* subpath re-exports the corresponding prosemirror-* package, including its TypeScript types. Domternal packages use these entry points to share the same ProseMirror classes and plugins.

Install

@domternal/core already depends on this package. Add it directly when your own code imports from @domternal/pm/*, or when an extension's peer dependencies require it:

pnpm add @domternal/pm

The package declares Node.js 22 or later for tooling and has no peer dependencies. Use version 1.8.0 for all installed Domternal Free packages. Free 1.8.x extensions require @domternal/core and @domternal/pm peers in >=1.8.0 <2.0.0. Core 1.8.0 requires PM >=1.8.0 <2.0.0 at runtime.

Usage

Always import a subpath. There is no @domternal/pm root export.

import { Plugin, PluginKey } from '@domternal/pm/state';

export const documentChangeLogger = new Plugin({
  key: new PluginKey('documentChangeLogger'),
  view: () => ({
    update(view, previousState) {
      if (!view.state.doc.eq(previousState.doc)) {
        console.log(view.state.doc.toJSON());
      }
    },
  }),
});

Register a plugin through an extension's addProseMirrorPlugins() hook or editor.registerPlugin(). See custom extensions and dynamic plugins.

Entry points

Every subpath supports ESM, CommonJS, and TypeScript:

| Import | Re-exports | | --- | --- | | @domternal/pm/commands | prosemirror-commands | | @domternal/pm/dropcursor | prosemirror-dropcursor | | @domternal/pm/gapcursor | prosemirror-gapcursor | | @domternal/pm/history | prosemirror-history | | @domternal/pm/inputrules | prosemirror-inputrules | | @domternal/pm/keymap | prosemirror-keymap | | @domternal/pm/model | prosemirror-model | | @domternal/pm/schema-list | prosemirror-schema-list | | @domternal/pm/state | prosemirror-state | | @domternal/pm/tables | prosemirror-tables | | @domternal/pm/transform | prosemirror-transform | | @domternal/pm/view | prosemirror-view |

Avoid duplicate ProseMirror copies

ProseMirror compares objects by identity. Loading two copies can cause fragment conversion errors, keyed-plugin collisions, and broken selections. Prefer these subpaths over direct prosemirror-* imports in code that interacts with Domternal.

Other dependencies and linked workspaces can still introduce duplicates. The single-copy guide explains runtime diagnostics and the package-manager and bundler fixes, including collaboration integrations.