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

@preferred-markdown-stream/renderer

v0.6.0

Published

Framework-agnostic streaming markdown render pipeline shared by the Vue and React packages

Readme

@preferred-markdown-stream/renderer

The framework-agnostic streaming Markdown pipeline shared by @preferred-markdown-stream/vue and @preferred-markdown-stream/react. Most applications should depend on one of those packages instead of this one.

It contains everything that is not framework-specific:

  • the markdown-it renderer plugin that emits a node tree through a TreeAdapter (each framework supplies one: Vue builds vnodes directly, React builds mutable intermediate nodes finalized into elements),
  • the frozen-prefix incremental renderer (createIncrementalMarkdownRenderer),
  • the markdown runtime factory with lazy Shiki/KaTeX loading (createMarkdownRuntime),
  • the mermaid loader registry and progressive fence renderer (configureMermaid, createMermaidController),
  • code-block line splitting for per-line fade-in (parseCodeBlockLines),
  • typewriter smoothing (createSmoothStreamController).

Writing an adapter for another framework

Implement TreeAdapter<N> (see src/adapter.ts for the contract), create a module-level runtime with createMarkdownRuntime({ adapter, codeBlockComponent, mermaidComponent }), and drive createIncrementalMarkdownRenderer(runtime) with (content, loading) on every stream update. The returned nodes reuse the document's frozen prefix by object identity — keep handing them to your framework unchanged and re-renders of settled content stay O(1).

Component styles (code block toolbar, mermaid container) are published via @preferred-markdown-stream/renderer/styles.css; the fade-in animation itself lives in @preferred-markdown-stream/core/styles.css.