-
Notifications
You must be signed in to change notification settings - Fork 178
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
🙏 Make typedoc-plugin-markdown
works with MDX2
#305
Comments
thanks - agreed this should be the default. Docusaurus doesn't (yet) support MDX2 which is why its done like this, but will take a look at a workaround for that. |
I was on a similar journey and decided to just tell Nextra to interpret the files as regular Markdown: I think it does not make sense(?) to use MDX as the content would look weird in IDEs like VSCode, but correct me if you disagree. |
@tgreyuk , awesome to see this land in the next version of the plugin! :) |
This version is still compatible with MDX V1, is my assumption correct? |
Is this closed by 3.17.0 ? |
Is mdx 2 or 3 (released Oct '23) going to be in the upcoming v4 release? |
Looking at the migration guide there is no output that will cause any breaking change. Additionally the output is parsed and checked with remark-mdx. So yes the intention is that both mdx2 and 3 is supported. |
Excellent, I think the key feature of mdx3 is the ability to use the await inside of it. |
Currently using
typedoc-plugin-markdown
with MDX2 can't be possible as starting from MDX2 it's necessary to escape{
and<
open brackets because MDX2 parses<
as JSX tag and{
as JS expression.typedoc-plugin-markdown
escapes only>
closing bracket but it's unnecessary, also he adds double whitespace before}
closing bracket that also redundant.I fixed these issues in
[email protected]
in the following patch:P.S. I hope one day I will be able to remove the unnecessary patch and the support of MDX2 in
typedoc-plugin-markdown
will be out-of-box.The text was updated successfully, but these errors were encountered: