-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
Unable to load mdx-embed after updating to MDX 2 #247
Comments
I've been wrestling with this issue for a while myself - @PaulieScanlon is there anything we can do to help here? |
Hey @mbifulco. I'm close to being able to investigate this. Gatsby released v4 of their plugin earlier this week with MDX 2 support. At present this package is only tested with MDX 1. Stay tuned! |
Just discovered I also suffer from this issue as I'm trying to migrate to MDX 2. Is there any way for me to help move this forward? |
@dsebastien Hey. I'm currently in the process upgrading all packages to MDX 2. Hopefully early next week I'll have an alpha cut ready for you to try out. |
For a quick fix, I've been able to work around this by converting: import { CodeSandbox, Gist, Tweet, YouTube } from "mdx-embed"; to import { CodeSandbox } from "mdx-embed/dist/components/codesandbox";
import { Gist } from "mdx-embed/dist/components/gist";
import { Tweet } from "mdx-embed/dist/components/twitter";
import { YouTube } from "mdx-embed/dist/components/youtube"; |
Any news about this issue? |
Struggling with this issue as well. |
Describe the bug
I am using mdx-embed in my nextjs application along with next-mdx-remote package. I have upgraded the next-mdx-remote package to 4.1.0 which has new MDX 2 features. After upgrading I am getting the following error in mdx-embed package
Since, MDX 2 migrated to use complete ESM packages, the
require
import of mdx-embed is throwing error. Is it possible to compile this package in ESM?To Reproduce
My branch with the upgraded packages - https://github.com/payapula/blog/tree/feature/next_chakra_upgrades_react_18
npm install
npm run dev
Expected behavior
There should not be any errors referring to
mdx-embed
pacakgeScreenshots
Desktop (please complete the following information):
Additional context
I think if we can migrate this project to ESM, we could solve this issue. Any help on this would be appreciated. Also happy to contribute PRs.
The text was updated successfully, but these errors were encountered: