-
-
Notifications
You must be signed in to change notification settings - Fork 205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Mermaid Diagrams Not Rendered in Exported PDF #342
Comments
Link to #337 |
I found changing the mermaid server to "https://cdn.jsdelivr.net/npm/[email protected]/dist/mermaid.min.js" worked to fix the issue. |
I had other issues with every mermaid 10.x release. Some failed to render completely, some had syntax errors. Mermaid v10 had a number of breaking changes, so maybe that is the reason for the problems. I switched to |
Thanks, only this version worked for me. |
Same for me! Mermaid v9.4.3 is also working on my end. |
unfortunately, neither the default, nor 10.4.0, nor 9.4.3 server renders my
P.S. there is logging in the source code, but I didn't see any log files at |
Running into a similar problem here, my |
As of today, this solution worked for me. Thanks |
It works, but seems like it's only working for 'mature' components. With https://cdn.jsdelivr.net/npm/[email protected]/dist/mermaid.min.js (and 10.7) and https://cdn.jsdelivr.net/npm/[email protected]/dist/mermaid.min.js" the output is |
Description:
When attempting to export a Markdown file containing Mermaid diagrams to PDF using the "Markdown PDF" extension in VSCode, the resulting PDF does not render the Mermaid diagrams. Instead, it displays the raw Mermaid code.
Reproduction Steps:
.md
) containing a fenced code block with themermaid
language identifier.Markdown PDF: Export (pdf)
from the VSCode command palette.Expected Behaviour:
The PDF should display a rendered Mermaid diagram corresponding to the code in the Markdown file.
Actual Behaviour:
The PDF displays the raw Mermaid code instead of the rendered diagram.
The text was updated successfully, but these errors were encountered: