Adapters and Plugins

Adapters and plugins extend VibeFlui without changing portable schemas. They are installed as separate packages, then registered through FluiKitProvider.

Adapter pages

• Core Package
• Shadcn Plugin
• Tailadmin Plugin
• React Query Plugin
• React Select Plugin
• Editors Plugin
• Ant Design Plugin
• Mantine Plugin
• Material UI Plugin

Package map

Plugin setup pattern

Optional packages export plugin factories. Some also export a prebuilt plugin constant or alias; check the package page before importing one.

import { FluiKit, FluiKitProvider } from "@vibeflui/core";
import { createShadcnPlugin } from "@vibeflui/shadcn";

const shadcnPlugin = createShadcnPlugin();

export function UsersPage() {
  return (
    <FluiKitProvider plugins={[shadcnPlugin]}>
      <FluiKit schema={usersSchema} data={usersData} />
    </FluiKitProvider>
  );
}

FluiKitProvider merges plugin registry entries, providers, messages, themes, adapters, and inspector panels. Direct registry, provider, and message props override plugin-provided values when they use the same keys.

Runtime slots

Plugins can register these runtime slots:

Related docs

• Field Adapters
• Registry Renderers
• Registry Keys