-
Notifications
You must be signed in to change notification settings - Fork 133
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
TypeError: _jsxDEV is not a function #324
Comments
This issue seems likely to be solved by this #307 (comment) |
Yes that worked for me. For reference, setting |
Hi y'all, this should be addressed by #323, try out 4.2.1 and let me know! |
Can confirm that |
Interesting enough, I've updated to the latest next-mdx-remote with renovate notification and it started breaking with something that seems to be an opposite error. Do you think you might know what could cause it or should share more information about the setup in a separate issue? Downgrading to 4.2.0 solves the issue |
same problem for me as @blvdmitry |
if you do a full re-install this should be fixed:
|
Tried 5 different ways of uninstalling because I use yarn and lerna and it worked in the end. Thanks for the tip! |
This issue still exist with |
this issue still exist with "next-mdx-remote": "4.3.0" and "next": "^13.1.6" T_T |
this issue still exist with |
alternative solution: mdxOptions: { development: process.env.NODE_ENV === 'development' } |
Getting an error on next v13.0.2 and next-mdx-remote v4.2.0
Everything works fine till I insert
The text was updated successfully, but these errors were encountered: