Skip to content
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

UI Components from common library (HeroUI formerly NextUI) throwing errors after upgrading to Nextra v4 #4196

Open
flanagankp opened this issue Feb 11, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@flanagankp
Copy link

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:

  1. Basic reproducing case setup with Nextra getting started guide and most basic HeroUI configuration: https://github.com/flanagankp/heroui-nextrav4

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.

Image

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.

@flanagankp flanagankp added the bug Something isn't working label Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant