You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! I'm developing a custom component that requires dynamic client-side Markdown rendering. Part of the content is fetched via API and needs rendering with the same capabilities as Vitepress default theme (code highlighting, custom containers, etc.).
Attempted Solutions
Identified createMarkdownRenderer in the source code, but this API appears to require Node.js environment (e.g., fs module for code snippet imports), making browser usage problematic.
Noted that the <Content /> component handles Markdown rendering, but its build-time pre-rendering design seems incompatible with dynamic content scenarios.
Humble Request
Would it be possible to consider providing any of these solutions:
Browser-compatible lightweight variant of @vitepress/markdown
If there's currently no existing solution, would the team consider adding documentation about these technical boundaries? Such clarification would be immensely helpful for custom component developers. Thank you sincerely for your time!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Context
Hello! I'm developing a custom component that requires dynamic client-side Markdown rendering. Part of the content is fetched via API and needs rendering with the same capabilities as Vitepress default theme (code highlighting, custom containers, etc.).
Attempted Solutions
createMarkdownRenderer
in the source code, but this API appears to require Node.js environment (e.g.,fs
module for code snippet imports), making browser usage problematic.<Content />
component handles Markdown rendering, but its build-time pre-rendering design seems incompatible with dynamic content scenarios.Humble Request
Would it be possible to consider providing any of these solutions:
@vitepress/markdown
Additional Notes
If there's currently no existing solution, would the team consider adding documentation about these technical boundaries? Such clarification would be immensely helpful for custom component developers. Thank you sincerely for your time!
Beta Was this translation helpful? Give feedback.
All reactions