Can we get some more guidance/docs on the recent development runtime change in 2.2?

[joostdecock]

Answer: https://github.com/orgs/mdx-js/discussions/2203#discussioncomment-4491981 (edited by wooorm)

The upgrade from 2.1 to 2.2 broke all of my MDX content with a frustrating error:

_jsxDEV is not a function

Looking into what changed, it seems this is related to #2045 by @remcohaszing

Now I don't pretend to understand all the intricate details, but what I do know is:

• This was a breaking change for me in a minor version bump. Not the end of the world, but just FYI, that's unexpected
• Setting development: false does not sidestap this issue for me. Short of NODE_ENV=production (or downgrading) I have yet to figure out how to resolve this.

I appreciate that this was debated as being a non-breaking change so maybe I'm doing something dumb which is why it breaks for me. But it would be nice to get some insight into what's going on and why development: false doesn't seem to fix it.

In my code, I'm doing what's documented under MDX on demand: https://mdxjs.com/guides/mdx-on-demand/

[joostdecock]

In case other people struggle with this, this is the current workaround I have put in place:

import { run } from '@mdx-js/mdx'
import * as runtime from 'react/jsx-runtime'
// ...
await run(mdx, { ...runtime, jsxDEV: runtime.jsx })

But I'd like to understand rather than work around this issue.

[joostdecock]

Thank you for taking the time to get back to my @remcohaszing 🙏

After a night of sleep, I think I've figured it out, and in retrospect it of course all makes sense.
Here's what I currently understand to be the gist of it:

• The develop: false setting does in fact side-step/resolve the issue but it must be passed to compile() and not to run().
• This would not constitute a breaking change for scenarios where the runtime is auto-added. But it is a breaking change for the MDX on demand behavior described.

I will submit a PR to add a note to the MDX on-demand documentation to make it easier for people in similar situtation to avoid getting bitten by this.

Thanks for all your hard work, and merry Christmas (if that's your thing) 🎄 🎅

[joostdecock]

#2204

[wooorm]

@remcohaszing can you update your code above to pass development to compile instead of run?
Other people might find this post and try to use your code, which is incorrect.

[colinsteidtmann]

Hey, I found this post after running into the same issue. Thanks y'all.

[ng-hai]

Thanks for the solution