Next.js: Theme UI's MDX Components Not Rendering in 9.4

Created on 18 May 2020  路  8Comments  路  Source: vercel/next.js

Bug report

Describe the bug

In my project raam, I'm trying to upgrade to Next 9.4. Unfortunately my ThemeProvider (from Theme UI) is no longer applying components to MDX:

PR: https://github.com/joe-bell/raam/pull/21
Demo: https://raam-git-chore-next-94.joebell.now.sh/

Is there something that needs to be done on my side/Theme UI's side to support fast refresh?

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

  1. Go to https://raam-git-chore-next-94.joebell.now.sh/

Expected behavior

The MDX content should render with the components I've defined, like the do with Next 9.3 in raam.joebell.co.uk

Screenshots

Before

Screenshot 2020-05-18 at 16 56 02

After

Screenshot 2020-05-18 at 16 55 51

System information

  • OS: macOS
  • Browser (if applies): N/A all browsers.
  • Version of Next.js: 9.4.1
  • Version of Node.js: 13.8.0
bug needs investigation

All 8 comments

Hey @joe-bell, shooting in the dark here, but I recently came across this issue on next-mdx-enhanced, perhaps it may be connected? https://github.com/hashicorp/next-mdx-enhanced/issues/53. I'm aware it's not the same package you're using for your mdx but it could be a related issue.

Thanks for the heads up @aizkhaj, sounds like there's a possibility this could be related

Digging into this a little more, I think it might be related to @next/mdx.

I was able to update a separate project using next-mdx-enhanced without a hitch, but this issue still remains in the repro provided on the latest version of Next.js

This appears to be fixed in 9.5! Thanks @Timer and team 馃帀

9.4: https://raam-git-chore-next-94.joebell.vercel.app/
9.5.1: https://raam-git-dependabot-npmandyarnnext-951.joebell.vercel.app/

@joe-bell any chance you can share a basic reproduction of your working setup? Or any hints on how you got it working? Seems to be very temperamental, still. I couldn't get it to work even with a fresh setup. And seems like others have the same problem. Might just be a single dependency version or so, I tried so many combinations over the last couple days. Any hints are greatly appreciated.

@jonashaefele there are links to an example in the description 馃檪

Thanks @joe-bell! Maybe I'm blind today but I only found links to the deployment not the repo. But just realised the branch for it is still public on your raam repo, will have a dig through and compare to my config. Thanks!

@jonashaefele no worries! Good luck and keep us posted

Was this page helpful?
0 / 5 - 0 ratings