-
Notifications
You must be signed in to change notification settings - Fork 12
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
Support mermaid v10 #28
Comments
For anyone arriving here looking for how they can get their diagrams back up in running, the Mermaid CHANGELOG.md has the answer: Fix your imported mermaid version to <script src="https://cdn.jsdelivr.net/npm/mermaid@9/dist/mermaid.js"></script> I had a look at creating a PR, but found myself quickly in a space that I was unaware of before. If you consider yourself good at navigating the ESM v CJS situation cropping up with cdns hosting up npm etc, this could be a cake walk for you. I'd also really love to see an experienced path through this fix in a PR. I understand the problem, but I'm not satisfied with any solutions I have yet read about. |
We are also facing same problem in our document site where mermaid diagrams are not rendering all of a sudden. Downgrading the version to 9 seems to fix the issue. |
I've made a PR correcting this issue #30. |
Thank you @corentinleberre for the PR. I tagged and publish a new version (v2). The README has been updated accordingly. |
These should work right? |
Hey! This package has been updated yesterday to v2. That's why it may not work on your setup currently. `<script type="module"> |
@corentinleberre , |
From v10, mermaid is ESM only.
So window.mermaid will not be available natively.
Also, mermaid.init is deprecated and replaced with mermaid.run.
mermaid-js/mermaid#4115
The text was updated successfully, but these errors were encountered: