# prosemirror-markdown: markdown-it v15 support and npm release

**URL:** <https://discuss.prosemirror.net/t/prosemirror-markdown-markdown-it-v15-support-and-npm-release/9124>\
**Category:** Uncategorized\
**Created:** [November 4, 2026, 10:42am UTC](https://discuss.prosemirror.net/t/prosemirror-markdown-markdown-it-v15-support-and-npm-release/9124 "2026-11-04T10:42:22Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![asblanco](https://discuss.prosemirror.net/user_avatar/discuss.prosemirror.net/asblanco/32/4835_2.png) [@asblanco](https://discuss.prosemirror.net/u/asblanco)\
**Post date:** [November 4, 2026, 10:42am UTC](https://discuss.prosemirror.net/t/prosemirror-markdown-markdown-it-v15-support-and-npm-release/9124/1 "2026-11-04T10:42:22Z")

</div>

Could `prosemirror-markdown` add support for markdown-it v15 and publish a corresponding npm release?

We use `prosemirror-markdown` in `@stackoverflow/stacks-editor` and are upgrading to markdown-it 15.0.3. The current `prosemirror-markdown` 1.13.9 release still depends on `markdown-it ^14.0.0` and `@types/markdown-it ^14.0.0`.

markdown-it v15 bundles its own TypeScript declarations and no longer exports internal paths such as `markdown-it/lib/token.mjs`. Using its tokenizer with the current prosemirror-markdown declarations produces incompatible `MarkdownIt`/`Token` types, including string-versus-number token attribute differences.

An upstream release with native v15 types would let us use the standard npm package instead of maintaining a downstream fork. Is this upgrade planned, or is there a preferred way to help move it forward?

Migration guide: [markdown-it/docs/migration/migration\_v15.md at 15.0.3 · markdown-it/markdown-it · GitHub](https://github.com/markdown-it/markdown-it/blob/15.0.3/docs/migration/migration_v15.md)

I tried the upstream issue tracker first, but its GitHub sign-in currently returns HTTP 500, so I’m asking here instead.