EnterUI
DocsComponentsThemesExamplesDonation
Get Started
  • Overview
  • Introduction
  • Installation
  • SSR & Next.js
  • SolidJS Renderer
  • Styling Philosophy
  • Theming
  • Accessibility
  • Production Checklist
  • Migration & Versioning
  • TroubleshootingResolve styling, rendering, and integration issues.
  • New components
  1. EnterUI
  2. /Docs
  3. /Getting Started
  4. /Troubleshooting
Updated 3 October 2026

Troubleshooting

Common setup, rendering, and accessibility issues.

#Styles Are Missing

Confirm both CSS files are imported and that the theme import comes first.

Code
import "@froggdesign/theme/styles.css";
import "@froggdesign/enter-ui-react/styles.css";

#Dark Mode Does Not Apply

Set data-theme="dark" on a root element that contains the application. EnterUI reads CSS variables from the active theme scope.

Code
<html lang="en" data-theme="dark">
  <body>{children}</body>
</html>

#Dialog Or Menu Content Does Not Appear In SSR Markup

Portal-based content is browser-rendered. Test trigger semantics in SSR and open content in jsdom or browser tests.

#Trigger Loses Keyboard Behavior

When using asChild, pass a semantic focusable element:

Code
<DialogTrigger asChild>
  <button type="button">Open</button>
</DialogTrigger>

#Form Error Is Not Announced

Use FormField with a single child control, or manually connect the control to the error with aria-describedby and aria-invalid.

#Duplicate React Versions

If hooks or context fail unexpectedly, check that the app resolves one React and React DOM version compatible with the package peer dependency range.

PreviousMigration & Versioning
NextNew components
On this page
  • Styles Are Missing
  • Dark Mode Does Not Apply
  • Dialog Or Menu Content Does Not Appear In SSR Markup
  • Trigger Loses Keyboard Behavior
  • Form Error Is Not Announced
  • Duplicate React Versions