shadcn
shadcn
I see. Can you try wrapping `children` in the `MDXProvider` from core? ```diff + import { MDXProvider } from "@reflexjs/gatsby-theme-core" - {children} + < MDXProvider >{children}
Did this fix the warnings? Let's add a `ThemeProvider` to layout and see if it picks up the theme. ```diff + import { ThemeProvider } from "theme-ui" + import theme...
Seems to be coming from `gatsby-plugin-layout`. Removing it fixes the theme: https://codesandbox.io/s/merging-forked-lxbeh I'll take a look at how we can get `gatsby-plugin-layout` and `mdx` to work together.
Hmm. I'll see if I can reproduce this. So builds work but incremental builds fail?
I still haven't been able to reliably reproduce this issue. Is this still happening?
@454de6e Thanks. This is helpful. I'm going to try and reproduce this locally.
@LocTran016 did you figure this out? Looks like the site is running? https://loctran016.github.io
@LocTran016 Looks like someone else had the same issue. Can you take a look at the following: https://spectrum.chat/mdx/general/resolved-problems-updating-to-mdx-v2-w-yarn-workspaces~126eddd4-942f-4e8b-9064-de45e8b4a4d9?
What happens if you remove gatsby-plugin-mdx from your package.json? Reflex will already pull this in as a dependency.
This is a change in the types for v2. Can you change your theme fontWeights from string to numbers? ```diff fontWeights: { - hairline: "100" + hairline: 100, ``` https://github.com/reflexjs/reflexjs/blob/e5768a97c410fb0ef2fc0e792917654a9af1d41e/packages/reflexjs/stubs/base.theme.js#L106-L116