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

@visimer/core

v1.1.2

Published

Headless bidirectional editing engine for Mermaid diagrams: lossless CST, semantic graph, ops compiled to minimal text edits.

Readme

@visimer/core

Headless bidirectional editing engine for Mermaid diagrams. Text is the source of truth: a lossless CST and per-type semantic graphs turn visual operations (rename, connect, reorder, restyle) into minimal text edits against your actual Mermaid source. Zero DOM dependencies.

import { MermaidWysiwygEditor } from '@visimer/core'

const editor = new MermaidWysiwygEditor({ code: 'flowchart TD\n  A --> B' })
editor.dispatch({ type: 'renameNode', id: 'A', label: 'Start' })
editor.code // 'flowchart TD\n  A[Start] --> B'
editor.undo()

Bring your own code editor

bindTextPane syncs the engine with any code editor behind a five-method adapter. For CodeMirror use @visimer/codemirror, for Monaco use @visimer/monaco; both are implementations of this contract. For anything else, implement the adapter:

import { bindTextPane } from '@visimer/core'

const binding = bindTextPane(editor, {
  getText: () => /* current document text */,
  applyEdits: (edits) => /* apply {start, end, text} offsets to the document */,
  setText: (text) => /* replace the whole document (resync safety net) */,
  setHighlights: (spans) => /* highlight the selected entities' ranges */,
  revealPosition: (offset) => /* optional: scroll an offset into view */,
})

// then wire your editor's events:
//   document changed  -> binding.notifyTextChange()
//   caret moved       -> binding.notifyCaretMove(offset)
//   undo/redo keys    -> binding.undo() / binding.redo()

Typing flows into the engine, engine changes come back as minimal edits, entity selection syncs both ways, and undo/redo shares the canvas history stack. The notify methods no-op while the binding is applying engine edits, so there is no echo loop to guard against.

Pairs with @visimer/dom (interactive canvas). Docs: github.com/inkeep/visimer