-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
[gatsby-plugin-mdx] + [gatsby-recipes]: Mixed mdx versions (2.x alpha being pulled in) #27278
Comments
I'm tracing an on/off mdx issue over a few weeks - it presents itself between package locks with yarn v1. @KyleAMathews helped us switch gatsby-recipes to mdx v2 in #24595. I'm having an issue where I'm getting mdx v2-next packages mixed into my lockfile (alongside 1.6.x pinned by me and gatsby-plugin-mdx) and wondering if that could causing hard-to-trace mdx issues. I believe it is coming from gatsby-recipes. Is there any way you think gatsby-plugin-mdx and gatsby-recipes could cause an issue with wanting separate versions of mdxjs? P.S. If anyone else has bumped into a similar issue and can provide a reproducible test case please chime in! |
Thank you @KyleAMathews! @pieh @KyleAMathews Any preference if I close this or keep it open for now? |
Let's keep this open until it's solved. I linked In the meantime, you can try those changes out by using |
Description
This is leading to hard-to-trace issues since:
Pinning were originally changed in 07085fa / #24595
Steps to reproduce
This can end up installing both mdx 2.0.0 and 1.6.6 simultaneously, causing hard to trace issues in projects since its picked up implicitly
Expected result
What should happen?
Actual result
Mixed versions of mdx being installed
Environment
Run
gatsby info --clipboard
in your project directory and paste the output here.The text was updated successfully, but these errors were encountered: