Skip to content
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

Closed
lorenzejay opened this issue Dec 27, 2022 · 13 comments
Closed

TypeError: _jsxDEV is not a function #324

lorenzejay opened this issue Dec 27, 2022 · 13 comments
Labels
bug Something isn't working

Comments

@lorenzejay
Copy link

Getting an error on next v13.0.2 and next-mdx-remote v4.2.0

Everything works fine till I insert

<MDXRemote {...source} components={{ Image }} />

Screenshot 2022-12-26 at 7 41 50 PM

@mabdh
Copy link

mabdh commented Dec 27, 2022

This issue seems likely to be solved by this #307 (comment)

@lorenzejay
Copy link
Author

This issue seems likely to be solved by this #307 (comment)

Yes that worked for me. For reference, setting development: false will fix.

BlakeRain added a commit to BlakeRain/blakerain.com that referenced this issue Dec 30, 2022
@devzom
Copy link

devzom commented Jan 3, 2023

@BRKalow
Copy link
Contributor

BRKalow commented Jan 5, 2023

Hi y'all, this should be addressed by #323, try out 4.2.1 and let me know!

@itsnitinr
Copy link

Can confirm that 4.2.1 works and solves this issue. Thanks!

@BRKalow BRKalow added the bug Something isn't working label Jan 5, 2023
@BRKalow BRKalow closed this as completed Jan 5, 2023
@blvdmitry
Copy link

blvdmitry commented Jan 9, 2023

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?

image

Downgrading to 4.2.0 solves the issue

@dimaMachina
Copy link

same problem for me as @blvdmitry

@BRKalow
Copy link
Contributor

BRKalow commented Jan 12, 2023

if you do a full re-install this should be fixed:

npm uninstall next-mdx-remote && npm install next-mdx-remote

@blvdmitry
Copy link

Tried 5 different ways of uninstalling because I use yarn and lerna and it worked in the end. Thanks for the tip!

@teddybee
Copy link

teddybee commented Feb 3, 2023

This issue still exist with
"next-mdx-remote": "4.3.0"
"next": "^13.1.6"

@auduongtuan
Copy link

this issue still exist with "next-mdx-remote": "4.3.0" and "next": "^13.1.6" T_T

@Eliot00
Copy link

Eliot00 commented Apr 12, 2023

this issue still exist with
"next": "^13.1.2",
"next-mdx-remote": "^4.4.1",

@sebanovo
Copy link

sebanovo commented May 3, 2024

alternative solution:

mdxOptions: { development: process.env.NODE_ENV === 'development' }

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests