-
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
Support for Docusaurus v3 #13
Comments
As long as Redux Toolkit is on Docusaurus 2, I probably won't add support myself - but I'd be open to PRs. One thing though: this looks like the output of this plugin isn't being parsed as mdx. There's not a lot this plugin can change about that in the first place - but maybe you were testing this in a .md file, not a .mdx file? |
Unfortunately, it is |
Seems like for Docusaurus 3, we need to pre-parse the JSX nodes we insert: facebook/docusaurus#9337 |
I believe #14 might fix this, but I have no Docusaurus 3 project. Could someone try it and report back? |
@aryaemami59 I believe you were setting something up for reselect? |
Yes sir, I'm looking at the potential memory leak problem in reselect at the moment, when I'm done I'll try running the docs and let you know the results. |
I recently tried upgrading some Docusaurus sites I maintain to v3, and it seems like
remark-typescript-tools
doesn't work so well with Docusaurus v3 (or maybe MDX v3?). Here are some screenshots to illustrate what happens:The
import
statements appear as plain text:So do the actual
Tabs
andTabItem
components:Just checking if you're planning on supporting Docusarus v3? Thanks!
The text was updated successfully, but these errors were encountered: