Releases: quantizor/markdown-to-jsx
markdown-to-jsx@9.8.2
Patch Changes
- 47408cd: Parsing is significantly faster, around 40% on large documents, with the biggest gains on link-heavy and code-heavy content. Also fixed an edge case where a reference definition split across blockquote lines could be matched by a link using the raw, unnormalized label.
- 47408cd: Documents with many bold or italic spans now parse in a fraction of the time. Previously, parsing slowed down sharply as the number of emphasized spans grew, which could make very large or adversarial inputs hang.
- 47408cd: The
<Markdown>component no longer re-parses its content when a parent re-renders with unchanged props. Previously the rest-props object was reallocated on every render, which invalidated the internal compile cache and forced a full re-parse each time. - 47408cd: Text on its own line after a nested HTML element (such as content following
</summary>inside<details>) now renders instead of being dropped or misplaced when no blank line separates them. This now behaves consistently across the React, React Native, Solid, and Vue outputs.
markdown-to-jsx@9.8.1
markdown-to-jsx@9.8.0
Minor Changes
- 51a68b1: React Native:
overridesnow work the same as on web. Pass an override forcode,pre,strong,em,del,blockquote,hr,h1–h6,ul,ol,li, orinputand it fires for parsed markdown — no more silent no-ops on inline emphasis, fenced code, headings, lists, or GFM task checkboxes. Thestylesprop is also tightened: each key is narrowed to the style type its component actually accepts (TextStyle,ViewStyle, orImageStyle), so passing anImageStyletoparagraphis now a compile-time error. Task list items now render with sensible row + center-aligned defaults so the checkbox and label sit on the same line out of the box; pass your ownstyles.listItemto opt out (e.g. for multi-line task labels). TheMarkdowncomponent additionally acceptsstring[]children to absorb the common JSX case where children arrive as a coalesced array.
markdown-to-jsx@9.7.16
markdown-to-jsx@9.7.15
Patch Changes
- 7ff0713: Fix React 19 RSC dev warning "Attempted to render without development properties"
markdown-to-jsx@9.7.14
Patch Changes
-
3df970f: Fix frontmatter detection silently consuming content when a thematic break (
---) starts the document. The colon-anywhere heuristic is replaced with proper YAML key-value validation, and a newdisableFrontmatteroption is added to skip detection entirely. -
c7e0d07: Fix
<hr>and other void HTML elements silently dropping all subsequent content when not followed by a newline (#856) -
c7e0d07: Fix HTML blocks with markdown content inside tables (#862) and restore CommonMark-correct behavior for HTML block content without blank lines (#860)
- Markdown lists inside HTML table cells now render as proper nested lists instead of breaking the table structure
- HTML block content on its own line without surrounding blank lines (e.g.
<div>\n*text*\n</div>) is now preserved as literal text per CommonMark Example 189 - HTML block content surrounded by blank lines (e.g.
<div>\n\n*text*\n\n</div>) continues to parse markdown as before (CommonMark Example 188)
-
0dfde05: Fix HTML compiler dropping the closing tag for empty non-void elements (e.g.
<p></p>rendered as<p>,<div></div>rendered as<div>) -
b0a7c68: fix: add key props to thead/tbody in table rendering to resolve React key warning (#858)
-
c7e0d07: Fix Vue adapter "Non-function value encountered for default slot" warning when using component overrides (#855)
markdown-to-jsx@9.7.13
Patch Changes
-
bcf178a: Fix streaming mode incorrectly stripping self-closing custom component tags (e.g.
<CustomButton />) and leaking incomplete trailing tags as escaped text in inline content.修复流式模式错误地移除自闭合自定义组件标签(如
<CustomButton />),以及内联内容中不完整的尾部标签作为转义文本泄漏的问题。स्ट्रीमिंग मोड में सेल्फ-क्लोज़िंग कस्टम कंपोनेंट टैग (जैसे
<CustomButton />) को गलत तरीके से हटाने और इनलाइन कंटेंट में अपूर्ण ट्रेलिंग टैग को एस्केप्ड टेक्स्ट के रूप में लीक होने की समस्या को ठीक करें।
markdown-to-jsx@9.7.12
Patch Changes
-
1c430ae: Fix missing TypeScript declaration files in published package. Add standalone post-build verification that fails the build when type declarations are not generated, independent of the bundler's plugin system.
发布包中缺少 TypeScript 声明文件的修复。添加独立的构建后验证,当类型声明未生成时构建失败,不依赖于打包器的插件系统。
प्रकाशित पैकेज में गायब TypeScript डिक्लेरेशन फ़ाइलों को ठीक करें। स्वतंत्र बिल्ड-बाद सत्यापन जोड़ें जो टाइप डिक्लेरेशन जनरेट न होने पर बिल्ड विफल करे, बंडलर के प्लगइन सिस्टम से स्वतंत्र।
markdown-to-jsx@9.7.11
Patch Changes
-
5eecb05: Skip rendering empty tbody when a table has only a header row and no data rows.
仅有表头行而无数据行的表格不再渲染空的 tbody。
केवल हेडर पंक्ति और कोई डेटा पंक्ति न होने पर खाली tbody रेंडर नहीं किया जाता।
-
130cc33: Suppress React 19 RSC development warning about missing internal properties on manually-created elements.
修复 React 19 RSC 开发模式下手动创建的元素缺少内部属性时产生的警告。
React 19 RSC के विकास मोड में मैन्युअल रूप से बनाए गए तत्वों पर आंतरिक गुणों की अनुपस्थिति संबंधी चेतावनी को ठीक किया।
markdown-to-jsx@9.7.10
Patch Changes
-
3daa41e: fix: strip trailing asterisks from bare URL href (fixes #839)
When a bare URL was wrapped in bold markdown (
**url**), the generated link'shrefincorrectly included the closing asterisks (e.g.href="/https://example.com/foo**"). The parser now trims trailing*from bare URLs so the href is correct. No consumer changes required.当裸 URL 包裹在粗体 markdown(
**url**)中时,生成的链接href错误地包含了闭合星号(例如href="/https://example.com/foo**")。解析器现在会从裸 URL 中去除尾部的*,使 href 正确。无需更改消费者代码。जब एक बेयर URL बोल्ड markdown (
**url**) में लपेटा गया था, तो जनरेट किए गए लिंक काhrefगलत तरीके से क्लोज़िंग एस्टेरिस्क शामिल करता था (जैसेhref="/https://example.com/foo**")। पार्सर अब बेयर URL से अनुगामी*को हटा देता है ताकि href सही हो। कोई उपभोक्ता परिवर्तन आवश्यक नहीं है। -
f520531: resolve emphasis delimiters closing before hard line breaks (two trailing spaces or backslash before newline)
解决在硬换行符(换行前有两个尾随空格或反斜杠)之前关闭强调分隔符的问题
हार्ड लाइन ब्रेक (न्यूलाइन से पहले दो ट्रेलिंग स्पेस या बैकस्लैश) से पहले एम्फ़ैसिस डिलीमिटर बंद होने की समस्या हल की
-
f520531: include _store on raw React elements unconditionally so React dev-mode validation works in all bundler environments
无条件地在原始 React 元素上包含 _store,使 React 开发模式验证在所有打包器环境中正常工作
सभी बंडलर वातावरण में React डेव-मोड सत्यापन काम करने के लिए रॉ React एलिमेंट्स पर बिना शर्त _store शामिल करें