-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Issues running in browser with react-markdown #1
Comments
I didn’t realize this at the moment of writing, but this is another breaking change. I’ll add this to the release notes. Both I recommend to stay on
A fix for this hast just been merged (mermaid-js/mermaid#4350 (comment)). This warning will go away soon. |
@remcohaszing They have merged it. I hope this issue gets fixed soon. |
remarkjs/react-markdown#680 is still open. As for the warning, that has been fixed. You may need to regenerate your lockfile. |
- pin rehype-raw to v6.1.1 while waiting for type updates remarkjs/react-markdown#769 - pin remark-mermaidjs to v4.1.1 according to a similar issue remcohaszing/rehype-mermaid#1
Based on the warning in the recent release of remark-mermaidjs, I've tried migrating to
rehype-mermaidjs
. I'm having some issues using it as a drop-in replacement for what I had previously.Here is what I'm doing:
This ends up crashing like so at runtime:
I also note that upon installation, I get this warning:
My goal is to be able to use a plugin to render Mermaid blocks in React Markdown. Perhaps this package isn't the best fit? Or maybe I'm missing something.
The text was updated successfully, but these errors were encountered: