mermaid version/feature support about mkdocs-material HOT 4 CLOSED

Thank for suggesting. Exact duplicate of #3171. Closing a duplicate.

from mkdocs-material.

As an addendum: we'll reconsider how to better integrate with third party JavaScript libraries in the future. Currently, MkDocs isn't really built for this. We could cram everything into config.extra, but that doesn't provide any safety or validation, so we'll need to find better approaches.

from mkdocs-material.

Note quite sure what I should take from that linked issue (especially since I cannot see the linked commits to understand what the changes were). When adding https://cdn.jsdelivr.net/npm/mermaid@10/dist/mermaid.esm.min.mjs to extra_javascript it will somehow load 10.9.0 and 10.7.0 at the same time but picking up 10.7.0 for the mermaid code blocks.

Changing the 10.7.0 to 10.9.0 in bundle.dd8806f2.min.js will make the new block-beta work by loading 10.9.0 a second time but so far I found no way I could load it together with zenuml ( first idea was to create an own .mjs that executes the loading code from the zenuml documentation, but even though that runs it seems there is always the material version being picked up to be called )

from mkdocs-material.

Note quite sure what I should take from that linked issue (especially since I cannot see the linked commits to understand what the changes were). When adding https://cdn.jsdelivr.net/npm/mermaid@10/dist/mermaid.esm.min.mjs to extra_javascript it will somehow load 10.9.0 and 10.7.0 at the same time but picking up 10.7.0 for the mermaid code blocks.

You know what, let's do that and stick to the latest major version. That should at least fix part of the problem. I've generalized the version range in 75d87ea.

from mkdocs-material.