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

comark-critic

v0.11.0

Published

CriticMarkup in Comark: insertions, deletions, substitutions, highlights, and comments as native <ins>, <del>, and <mark>, shown, accepted, or rejected.

Readme

comark-critic

npm version npm downloads license docs

CriticMarkup in Comark: suggested insertions, deletions, substitutions, highlights, and comments, rendered as native <ins>, <del>, and <mark> with a class each, or accepted or rejected. A parse plugin with no components, so it works in any renderer.

pnpm add comark comark-critic
import { parseMarkdown } from "comark";
import critic from "comark-critic";
import "comark-critic/style.css";

const document = await parseMarkdown(markdown, {
  plugins: [critic({ mode: "view" })],
});
The deploy waits when more than {--twelve--}{++fifteen++} pigeons sit on the roof.

Count them {~~after~>before~~} the stand-up, from the {==east window==}{>>Not the west one.<<}.

| Mark | Markdown | view | accept | reject | | --- | --- | --- | --- | --- | | Insertion | {++added++} | <ins class="ccm-ins"> | its text | nothing | | Deletion | {--removed--} | <del class="ccm-del"> | nothing | its text | | Substitution | {~~old~>new~~} | <del> then <ins> | the new text | the old text | | Highlight | {==this==} | <mark class="ccm-mark"> | its text | its text | | Comment | {>>why<<} | <span class="ccm-comment"> | nothing | nothing |

Text inside a mark is Markdown, and each mark opens and closes in one paragraph. One left open stays as written and adds a sentence to meta.issues.

Without the plugin, Comark reads {++added++} as attributes and drops the whole mark. Comark's {.class}, {#id}, and {{ bindings }} still work.

Styles

The marks' styles are in comark-critic/style.css, also exported as css: insertions tinted green, deletions struck through in red, highlights amber, and comments as muted notes with a speech bubble. Each mark has a class (ccm-ins, ccm-del, ccm-mark, ccm-comment), so they never restyle a ~~strikethrough~~. They read the shared tokens, so a shadcn/ui theme restyles them, and sit in the comark layer so your own rules win.

Credits

Syntax from CriticMarkup, and the modes from pymdownx.critic.