Fumadocs OpenAPI v12

We are pleased to announce the release of Fumadocs OpenAPI v12.

An API page used to be one component with a long list of render options. v12 splits it in two:

• a headless layer that owns the state and logic,
• the UI it renders through, which you can install and edit.

Options remain for the small tweaks, the rest is yours to replace.

Headless API PagesCopy Anchor Link

Everything outside fumadocs-openapi/ui renders nothing on its own.

createOpenAPIRenderer() takes your components and returns an <OpenAPIPage /> that accepts the props of generated pages:

'use client';
import { createOpenAPIRenderer } from 'fumadocs-openapi';
import { Operation } from '@/components/my-operation';
import { SchemaUI } from '@/components/my-schema';

export const OpenAPIPage = createOpenAPIRenderer({
  components: { Operation, SchemaUI },
});

Markdown, CodeBlock and Heading are filled in when you leave them out, so a custom UI starts from two components.

Under the page, hooks read its state:

See Headless for the full surface.

Install the UICopy Anchor Link

The entire UI of API pages, built on that layer, installed with Fumadocs CLI:

npx @fumadocs/cli add openapi/page

Your components/api-page.tsx is no longer needed:

import { OpenAPIPage } from '@/components/api-page'; 
import { OpenAPIPage } from '@/components/openapi/page'; 

Or take one part of it, and pass the rest through components:

'use client';
import { createOpenAPIPage } from 'fumadocs-openapi/ui';
import { Operation } from '@/components/openapi/operation';
import { Schema } from '@/components/api/schema';

export const OpenAPIPage = createOpenAPIPage({
  components: { Operation, SchemaUI: Schema },
});

What you install is UI, not a fork:

• the request pipeline of the playground stays in the package, an edited playground still drives the real one.
• Select and Input follow the Shadcn UI API, a project that already has them keeps its own.

@fumadocs/json-schemaCopy Anchor Link

The JSON Schema utilities of API pages are their own package, with no Fumadocs dependencies:

import { dereference, matches, mergeAllOf, sample, stringify } from '@fumadocs/json-schema';
import { bundle } from '@fumadocs/json-schema/bundle';

• bundle() is a separate entry because it reads files and URLs, everything else runs in the browser.
• @fumadocs/json-schema/react turns a schema into the data an API page draws. generateSchemaUI() flattens it, so your UI walks a map from $root instead of recursing.
• @fumadocs/api-docs is no longer published, its UI is now bundled into the integrations or installed with the CLI.

Smaller BundlesCopy Anchor Link

createOpenAPIBaseRenderer() is the renderer with nothing built in, it bundles only what you pass:

createOpenAPIBaseRenderer({
  shiki,
  codeUsages: createCodeUsageGeneratorRegistry().register(curl),
  components: { Operation, SchemaUI },
});

createOpenAPIRenderer() and fumadocs-openapi/ui register the full Shiki bundle, every code usage generator and TypeScript definitions for you.

The package entry is client-safe too. generateFiles() reads and writes files, so it ships stubbed under the browser condition, and a client component importing the renderer no longer pulls node:fs into the bundle.

MigrationCopy Anchor Link

Run a type check after upgrading:

npm run types:check

OptionsCopy Anchor Link

Render options that returned a component are components now:

 createOpenAPIPage({
-  schemaUI: { render: (props) => <Schema {...props} /> },
-  renderHeading: (props, depth) => <Heading depth={depth} {...props} />,
-  renderCodeBlock: (props) => <CodeBlock {...props} />,
-  renderMarkdown: (md) => <Markdown md={md} />,
+  components: { SchemaUI: Schema, Heading, CodeBlock, Markdown },
 });

• playground.provider is removed, the page provides the auth state of the playground.

• playground.render and generateTypeScriptDefinitions no longer receive ctx. Read the document from useOpenAPI().doc, or the doc passed to generateTypeScriptDefinitions.

• operation.APIExampleSelector is removed, install openapi/operation and edit the selector in usage-tabs.tsx.

• <PlaygroundClient /> reads the operation from useOperation(), its route, method, operation and pathItem props are gone:

  Copy Text

  playground: {
    render: () => <PlaygroundClient writeOnly readOnly={false} />,
  }

• The ctx of content render options is the render options of the page, what useRenderContext() returns. ctx.schema, ctx.SchemaUI and ctx._default_processMarkdown are removed, read them from useOpenAPI().doc and useComponents().

HooksCopy Anchor Link

The hooks of fumadocs-openapi/ui are replaced by the headless ones:

- const { route, examples, example, setExample, setExampleData } = useOperationContext();
+ const { path } = useOperation();
+ const { items, selected, select, update } = useExampleRequests();
+ // data of the selected example, replaces `addListener()`
+ const data = useExampleRequest();

useStorageKey() is removed, read the prefix from the page:

const { storageKeyPrefix } = useOpenAPI();
localStorage.getItem(`${storageKeyPrefix}my-key`);

Removed & MovedCopy Anchor Link

Also in v12Copy Anchor Link

• Code samples from x-codeSamples and generateCodeSamples are rendered when their id isn't a built-in generator.
• SchemaData.infoTags entries are data the UI renders: { label, value, block? } or { label, list }. Custom nodes ({ node }) still work, code reading tag.node must handle all shapes.

Thanks for supporting Fumadocs, share your upgrade experience on GitHub :)