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

@postkit/core

v0.2.0

Published

Portable Postkit document model, parsers, and serializers

Downloads

159

Readme

@postkit/core

Portable, versioned Postkit documents for moving structured content between HTML, Markdown, MDX, JSON, and renderers without depending on React.

import { parsePostkit, serializePostkit } from '@postkit/core';

const document = parsePostkit(feedItem.content, { format: 'html' });
const json = serializePostkit(document, { format: 'json' });

The HTML and MDX parsers are intentionally non-executable. They preserve safe semantic content and recognized Postkit annotations while discarding scripts, event handlers, unsafe URLs, and MDX expressions.

Formats

  • parsePostkitHtml(source) normalizes untrusted HTML into semantic nodes.
  • parsePostkitMarkdown(source) supports CommonMark and GFM lists, tables, autolinks, and strikethrough. Footnote references and definitions are preserved as literal text, not converted into linked footnotes.
  • parsePostkit(source, { format: 'mdx' }) supports literal MDX components and rejects expressions, spread props, imports, and exports.
  • parsePostkitJson(source) validates the versioned document format.
  • serializePostkit(document, { format }) writes HTML, Markdown, MDX, or JSON.

HTML serialization normalizes and allowlists semantic attributes. URL attributes must be strings with safe schemes; arrays cannot bypass URL validation.

Reference links and images resolve their Markdown definitions. Mixed inline HTML is parsed as a complete stream, retaining Markdown formatting between tags and passing the resulting tree through the HTML safety filter.

Markdown export escapes literal block markers, entities, and link/image destinations so text and URLs retain their meaning when reparsed. Task items export as disabled HTML checkboxes; HTML import recognizes leading checkboxes inside list items (including paragraph-wrapped GFM output) and recovers both checked and unchecked state.

Annotated HTML preserves Postkit component names and JSON-compatible props in data-postkit-* attributes. Serialization does not add a document wrapper by default; request one with documentElement when a transport needs a single root.

import { parsePostkitHtml, serializePostkitHtml } from '@postkit/core';

const document = parsePostkitHtml(rssItem.content);
const portableHtml = serializePostkitHtml(document, {
  documentElement: 'article',
});

Plain Markdown uses annotated HTML fallbacks for structures Markdown cannot represent. MDX output uses literal component tags and serialized data props; it never emits JavaScript expressions.

MDX serialization escapes literal braces and ESM-like text, keeps code fences isolated, and validates the generated syntax with the non-executable parser. Unrepresentable or executable output fails closed rather than returning unsafe MDX for a downstream compiler.

Documents use an explicit version so future schema changes can be migrated without guessing which representation a consumer received.

Parsing makes content non-executable, but an application still controls the component registry used to render component nodes and should expose only components appropriate for its trust boundary.

License

MIT