structyl is an open-source, TypeScript-first React component library with 90+ accessible components. It combines WAI-ARIA compliant headless primitives with Tailwind CSS v4 styled wrappers, a runtime theming system, and a first-class DataTable — all in independently-versioned npm packages.

How does structyl differ from shadcn/ui?

structyl ships as actual npm packages (pnpm add @structyl/styled) rather than copy-paste code snippets. It adds a runtime theming system that switches themes without a page reload, a feature-complete DataTable, 24+ React hooks, and 90+ components — significantly more than shadcn/ui out of the box.

How does structyl compare to Radix UI?

structyl builds on the same headless-first philosophy as Radix UI but adds a complete Tailwind-styled layer, runtime theming with CSS variables, dark mode, a DataTable, and chart components. Radix is primitives-only; structyl is a full component library ready to use.

Is structyl compatible with Next.js App Router?

Yes. All structyl components that use React hooks are marked with 'use client'. The library is SSR-safe and fully compatible with Next.js 15 App Router and React Server Components.

Does structyl support dark mode?

Yes. structyl includes a ThemeProvider that supports system, light, and dark modes. Theme switches happen instantly using CSS custom properties — no page reload required and no flash of unstyled content.

How do I install structyl?

Install the main package with: pnpm add @structyl/styled (or npm install @structyl/styled). Then wrap your app in ThemeProvider from @structyl/themes and add Toaster from @structyl/styled to your root layout.

Is structyl free and open source?

Yes. structyl is MIT licensed and completely free. All packages are published to npm under the @structyl scope.

Does structyl support TypeScript?

Yes. structyl is built with TypeScript strict mode throughout. All components export their prop types and the library ships with full type definitions. There is no any usage in the public API.

What styling system does structyl use?

structyl uses Tailwind CSS v4 for styling, tailwind-variants for type-safe variant APIs, and tailwind-merge for class conflict resolution. All colors and design tokens are CSS custom properties that integrate with the runtime theming system.

Does structyl have a DataTable component?

Yes. structyl includes a first-class DataTable in the @structyl/data-table package, built on @tanstack/table-core. It supports sorting, multi-column filtering, pagination, row selection, column resizing, and row virtualization via @tanstack/react-virtual.

Dialog API

View component

The full prop reference for the Dialog component. A window overlaid on the primary content, rendering the content underneath inert.

Import

tsx

import { Dialog } from '@structyl/styled';

Props

Root

Container component that manages dialog state and provides context to child components

Prop	Type	Default
open#	`boolean` Controlled dialog open state	—
defaultOpen#	`boolean` Initial open state when uncontrolled	false
onOpenChange#	`(open: boolean) => void` Callback fired when dialog open state changes	—
modal#	`boolean` Whether dialog is modal (blocks interaction outside, traps focus) or non-modal	true
children#	`React.ReactNode` Dialog content and subcomponents	—

Trigger

Button that toggles the dialog open state; extends HTML button element

Prop	Type	Default
asChild#	`boolean` Render as child element instead of button	—
className#	`string` CSS class name	—

Portal

Portals dialog content outside component hierarchy (typically to document body)

Prop	Type	Default
children#	`React.ReactNode` Content to portal	—
container#	`Element \| DocumentFragment \| null` DOM element to portal into; defaults to document.body	—
forceMount#	`boolean` Force-mount content to DOM even when dialog is closed	—

Overlay

Backdrop overlay behind dialog content; only renders when modal=true; extends HTML div element

Prop	Type	Default
asChild#	`boolean` Render as child element instead of div	—
forceMount#	`boolean` Force-mount overlay to DOM even when dialog is closed	—
className#	`string` CSS class name	—

Content

Main dialog container; extends HTML div element; contains title, description, and close button

Prop	Type	Default
asChild#	`boolean` Render as child element instead of div	—
forceMount#	`boolean` Force-mount content to DOM even when dialog is closed	—
onEscapeKeyDown#	`(event: KeyboardEvent) => void` Callback fired when Escape key pressed; call event.preventDefault() to prevent dismiss	—
onPointerDownOutside#	`(event: PointerDownOutsideEvent) => void` Callback fired when pointer down event occurs outside content	—
onInteractOutside#	`(event: PointerDownOutsideEvent \| FocusOutsideEvent) => void` Callback fired on any interaction outside content (pointer or focus)	—
onOpenAutoFocus#	`(event: Event) => void` Callback fired when focus moves into content on open; call event.preventDefault() to prevent	—
onCloseAutoFocus#	`(event: Event) => void` Callback fired when focus moves back on close; call event.preventDefault() to prevent	—
className#	`string` CSS class name	—

Title

Dialog title heading; renders as h2 element; extends HTML heading element

Prop	Type	Default
asChild#	`boolean` Render as child element instead of h2	—
className#	`string` CSS class name	—

Description

Dialog description text; renders as p element; extends HTML paragraph element

Prop	Type	Default
asChild#	`boolean` Render as child element instead of p	—
className#	`string` CSS class name	—

Close

Button that closes the dialog; extends HTML button element; includes built-in close functionality

Prop	Type	Default
asChild#	`boolean` Render as child element instead of button	—
className#	`string` CSS class name	—

Header

Convenience wrapper for dialog title section; styled div container

Prop	Type	Default
className#	`string` CSS class name	—

Anatomy

Import the parts and compose them together.

tsx

<Dialog.Root>
  <Dialog.Trigger />
  <Dialog.Portal>
    <Dialog.Overlay />
    <Dialog.Content>
      <Dialog.Title />
      <Dialog.Description />
      <Dialog.Close />
    </Dialog.Content>
  </Dialog.Portal>
</Dialog.Root>

Keyboard interactions

Adheres to the WAI-ARIA design pattern .

Key	Description
`Space`	Opens/closes the dialog from the trigger.
`Enter`	Opens/closes the dialog from the trigger.
`Tab`	Moves focus to the next focusable element; trapped within content.
`Shift + Tab`	Moves focus to the previous focusable element.
`Esc`	Closes the dialog and moves focus to the trigger.

Source code

If you didn't find what you need here, read the component implementation .