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

@stream-mdx/worker

v0.1.1

Published

Worker client utilities and shared worker helpers for the Streaming Markdown V2 pipeline

Downloads

844

Readme

@stream-mdx/worker

Worker client utilities and hosted worker bundle used by StreamMDX.

Most consumers interact with this package indirectly via <StreamingMarkdown />. You only need @stream-mdx/worker directly if you want explicit control over worker instantiation, MDX compilation parity helpers, or strict CSP setups.

Install

npm install @stream-mdx/worker

Hosted worker bundle (recommended)

For production, host the worker bundle from static assets (avoids blob: CSP requirements):

mkdir -p public/workers
cp node_modules/@stream-mdx/worker/dist/hosted/markdown-worker.js public/workers/markdown-worker.js

Then point StreamMDX at it:

<StreamingMarkdown worker="/workers/markdown-worker.js" />

Node / CLI worker threads

To run the hosted worker bundle in Node (e.g., Ink TUIs), use:

import { createWorkerThread } from "@stream-mdx/worker/node";

This spawns a worker_threads worker and installs WebWorker-like shims so the hosted bundle can run under Node.

MDX compilation parity helper

If you compile MDX on the server (e.g. Next.js API route), use the same compilation logic as the worker:

import { compileMdxContent } from "@stream-mdx/worker/mdx-compile";

See docs/REACT_INTEGRATION_GUIDE.md for the full wiring and parity notes.

Docs

  • React integration guide: docs/REACT_INTEGRATION_GUIDE.md
  • Security model / CSP: docs/SECURITY_MODEL.md
  • Plugins & custom worker bundles: docs/STREAMING_MARKDOWN_PLUGINS_COOKBOOK.md