streamdown replaces react-markdown for output that arrives half finished
A drop-in replacement for react-markdown, designed for AI-powered streaming.
At a glance
- What is it?
- streamdown is a TypeScript drop-in replacement for react-markdown, designed for AI-powered streaming.
- Who is it for?
- Adopt streamdown when you already render model output through react-markdown, and want a drop-in replacement designed for streaming. Leave it alone for plain static Markdown, where the streaming problem does not exist, and check that your Node version satisfies the repo's >=20 engine before touching the monorepo.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository last received commits 2 days ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- vercel/streamdown5,765 ★ · +136
| Repository | 2026-09-18 | 2026-11-15 |
|---|---|---|
| vercel/streamdown | 5.6k | 5.8k |
136 Stars in the last 58 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The problem is the half written block, not the formatting
streamdown is positioned as a drop-in replacement for react-markdown, designed for AI-powered streaming. It is written in TypeScript and lives in a monorepo alongside four plugin packages: @streamdown/code, @streamdown/cjk, @streamdown/math and @streamdown/mermaid.
npm i streamdown, then one @source line in globals.css
The install is one command:
npm i streamdownA hoisted node_modules turns the default path wrong
Without shadcn tokens the components lose their own styling
Plugins are opt in, and each one brings its own @source line
Four optional packages extend the renderer: `@streamdown/code`, `@streamdown/cjk`, `@streamdown/math` and `@streamdown/mermaid`. The root `build:packages` script builds them together with streamdown itself.
fallbackComponent fills gaps and does nothing else
The monorepo pins pnpm 10.30.3, Turbo and changesets
The repository is a pnpm workspace named `streamdown-monorepo`, marked private, with `apps/`, `packages/` and a `skills/` directory at the root. Its package manager field pins `[email protected]` and the engines field asks for `node >=20`.
Everything runs through Turbo: `build`, `dev`, `test`, `check-types`, `bench` and `bench:ui` are all `turbo run` wrappers. `build:packages` narrows the build to the five published packages, streamdown plus the math, code, cjk and mermaid plugins. Releases go through changesets, with `changeset:publish` running the build first. Linting runs through `ultracite check` and `ultracite fix`, Biome is pinned at 2.4.5, and TypeScript is pinned at 5.9.3. One dependency override is declared: `lodash-es` at `>=4.17.23`.
A LICENSE file sits at the root, but the repository's license field reads NOASSERTION, so check the file itself before you copy licensing terms into anything.
Editorial conclusion
Adopt streamdown when you already render model output through react-markdown, and want a drop-in replacement designed for streaming. Leave it alone for plain static Markdown, where the streaming problem does not exist, and check that your Node version satisfies the repo's >=20 engine before touching the monorepo.
Frequently asked questions
streamdown vs react markdown: what is the difference?
Streamdown presents itself as a drop-in replacement for react-markdown, designed for AI-powered streaming.
Does streamdown require Tailwind to render correctly?
You need a @source line in your global CSS so Tailwind can detect the utility classes Streamdown ships. The components also rely on shadcn/ui CSS custom properties for colors, radius and spacing, and without them you get missing backgrounds, missing borders or wrong spacing.
How do I set up streamdown in a monorepo?
Workspaces hoist dependencies to the root node_modules, so the @source path has to reach there from your CSS file, for example @source "../../../node_modules/streamdown/dist/*.js" from apps/web/app/globals.css. Adjust the number of ../ segments to your own layout.
What does fallbackComponent do in streamdown?
It renders tags that have no built-in renderer and are not overridden through components, which covers allowedTags custom elements and uncovered HTML tags such as span, em, div and br. Built-in entries and explicit components overrides still take precedence, so restyling h1, p or code means passing them in components.
Which optional plugins does streamdown ship?
@streamdown/code, @streamdown/cjk, @streamdown/math and @streamdown/mermaid.
Official sources
Was this useful?