-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Unhelpful error message when 0.x @astrojs/mdx used with Astro 3 #8985
Comments
Hey @JoshuaKGoldberg sorry for not responding earlier. I see that the commit no longer exists. Are you still having this problem? If not can we close the issue? Thanks. |
Oop, sorry, I don't know what force push I did to get rid of it 😅. I'd assume the issue still exists but will probably be less relevant as time goes on. It was quite irritating to discover the hard way when upgrading. |
Thanks for the issue. While I think it's nice to prevent hard breakage like these in the future, we don't have much bandwidth to fix this case at the moment. All packages should usually be upgraded to latest when upgrading Astro as well. And for that, #8525 may help with this. For now I'll close this issue. |
I had this same issue when attempting to rebuild my Astro site that wasn't touched for a year. I ended up using I then went to rebuild it using
I then installed Sharp using |
Astro Info
If this issue only occurs in one browser, which browser is a problem?
n/a
Describe the Bug
After upgrading all packages except
@astrojs/mdx
to the latest for Astro 3 (hooray! congrats again on the launch! 🥳), trying to visit or build a.mdx
page with frontmatter yields:What's the expected result?
pls work :c
Aside: I tried astro.new for a bit but it didn't give the error I wanted 😞 sorry! But this was reported on Discord too: https://discord.com/channels/830184174198718474/1162386580548362344
Repro steps:
pnpm install
pnpm build
Link to Minimal Reproducible Example
https://github.com/JoshuaKGoldberg/dot-com/tree/694445d (sorry)
Participation
The text was updated successfully, but these errors were encountered: