You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously all HeroUI (formerly NextUI) components worked fine being used directly in MDX files in Nextra v3 and earlier. Now certain components, throw an error when used directly in MDX files. This is reproducible with the Table components.
Note: Not all components fail like this, some like the Button or Card components are just fine (well their styling is not working but that's because HeroUI is still using tailwind 3, unrelated to this issue.)
In both Nextra v3 and v2 I was able to use the table components directly in MDX files without any errors. This is preventing my team from being able to upgrade to Nextra v4.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: macOS Sequoia 15.3
Browser: Chrome 132 and Arc 1.79.1
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
Previously all HeroUI (formerly NextUI) components worked fine being used directly in MDX files in Nextra v3 and earlier. Now certain components, throw an error when used directly in MDX files. This is reproducible with the Table components.
Note: Not all components fail like this, some like the Button or Card components are just fine (well their styling is not working but that's because HeroUI is still using tailwind 3, unrelated to this issue.)
To Reproduce Steps to reproduce the behavior:
Expected behavior
In both Nextra v3 and v2 I was able to use the table components directly in MDX files without any errors. This is preventing my team from being able to upgrade to Nextra v4.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: