Fix tab names that consist of a single JSX element
With parseMdx enabled, remarkCodeTab unwrapped a tab name that was entirely one JSX element and kept only its children, so icon-only names like tab="<Home />" rendered an empty trigger. Only paragraphs are unwrapped now, matching the behavior of fumadocs-core.
Support installing the API playground via Fumadocs CLI
npx @fumadocs/cli add fumadocs/openapi/playground
Use it with the playground.provider and playground.render options, see Customise UI.
Pass full props to schemaUI.render
It now receives the same props as the built-in Schema UI (including renderMarkdown and renderCodeblock), so a customised Schema UI can act as a drop-in replacement:
OpenAPI schema types from fumadocs-openapi (e.g. OperationObject, HttpMethods).
useRenderContext, useServerContext and useOperationContext from fumadocs-openapi/ui.
@fumadocs/base-ui@16.15.5
fumadocs-core@16.15.5
fumadocs-ui@16.15.5
Root types: version your docs with root: "<type>"
root in meta.json now accepts a string, the type of root folder. Root folders of the same type under the same parent are interchangeable, which is how you keep multiple versions of the same docs in one site:
{ "title": "1.0.0", "root": "version"}
{ "title": "2.0.0", "root": "version"}
The sidebar only shows the opened version, and docs layouts render a dropdown to switch between them. Switching keeps your place: it navigates to the same page in the other version (/docs/v1/guide to /docs/v2/guide), or its index page when the page doesn't exist there.
root: true is simply the default type, displayed as tabs. See Versioning for the guide and Root Type for the reference.
Tabs are grouped by root folder
Layout tabs are now grouped by the root folders on the current page's path, with one dropdown per group. This changes a few behaviours of the existing root: true tabs:
Clicking a tab navigates to the same page in the target folder when it exists, otherwise its index page as before.
With nested root folders, each level gets its own dropdown instead of one flat list. Tab lists (tabMode: 'top' on Docs layout, tabMode: 'navbar' on Notebook layout) show the innermost root: true group, and are hidden on pages outside of any root folder.
getLayoutTabs() includes typed root folders too, so a custom transform also decorates them. Custom tabs entries bound to a page tree folder are grouped the same way, other entries are appended to the root: true dropdown.
tabs={false} disables the dropdowns of typed root folders as well.
findProjection() in fumadocs-core/page-tree
Find the structural projection of a page in another root folder, the page at the same file path relative to the root folder:
import { findProjection } from 'fumadocs-core/page-tree';findProjection(v1, v2, page)?.url;
Add API Playground & Schema UI components
Install the UI of API integrations into your codebase:
intersection treated any difference in the type keyword as an impossible schema and returned false, so an allOf member using a type array (e.g. ['string', 'null'], emitted for nullable: true) merged with a typed member (type: 'string') produced false instead of type: 'string' — dropping every property of the schema in the Schema UI and the playground.
Intersecting overlapping type sets now keeps the shared members, and only genuinely disjoint types (e.g. ['string'] with ['number']) resolve to false.
Use the explicit title of composed schemas in Schema UI
mergeAllOf now keeps an explicit title as the display alias of the composed schema (ChildA | ChildB), skips titles already covered by the other side of an intersection (DerivedConfig, array<NamedItem>), and still combines the titles of untitled intersections (Readable & Writable).
Fix OpenAPI 3.0 example in external files crashing OpenAPIPage
The version upgrader ran after external documents were embedded under x-ext, where it can no longer classify schemas by their JSON path: a schema-level example from an external 3.0 file became an Example Object map instead of the JSON Schema examples array, crashing the schema UI with schema.examples is not iterable.
Each document is now upgraded before bundling embeds it. This also honors the external file's own declared OpenAPI version, so a 3.0 file referenced from a 3.1 document is upgraded too (previously it was skipped entirely).
Support OpenAPI 3.2 tag hierarchy in groupBy: 'tag'
generateFiles now follows the tag hierarchy introduced in OpenAPI 3.2: a tag with a parent becomes a folder nested inside its parent tag's folder (including the generated meta.json), and tags with a kind other than nav no longer form groups, matching their intent (e.g. badge).
Operations referencing undeclared tags or having no tags are no longer dropped silently, which previously could produce an empty output directory. Undeclared tags now form their own group, and untagged operations are grouped under an unknown folder with a warning.
@fumadocs/base-ui@16.15.4
fumadocs-core@16.15.4
fumadocs-ui@16.15.4
Fix Next.js <Link> not scrolling to top under docs layouts
The page container rendered <main style="display: contents">, which Next.js' scroll handler treats as a hidden element: display: contents generates no box, so its getBoundingClientRect() is all-zero, indistinguishable from display: none. The handler skips it (and the sticky TOC siblings) without ever descending into children, dropping the scroll-to-top on navigation entirely.
The <main> element in Docs, Notebook and Flux page containers is now a real grid item (display: grid; grid-area: main) wrapping the unchanged #nd-page article, which centers via the grid instead of mx-auto. Rendering is identical, but if your custom CSS has element rules on main that were previously inert, they now apply.
Fix OpenAPI 3.0 example in external files crashing OpenAPIPage
The version upgrader ran after external documents were embedded under x-ext, where it can no longer classify schemas by their JSON path: a schema-level example from an external 3.0 file became an Example Object map instead of the JSON Schema examples array, crashing the schema UI with schema.examples is not iterable.
Each document is now upgraded before bundling embeds it. This also honors the external file's own declared OpenAPI version, so a 3.0 file referenced from a 3.1 document is upgraded too (previously it was skipped entirely).
@fumadocs/base-ui@16.15.3
fumadocs-core@16.15.3
fumadocs-ui@16.15.3
Fix duplicated search result for pages whose description repeats in the content
Pages generated by Fumadocs OpenAPI emit the operation description as both the page description and a content section, so every endpoint page listed the same line twice in the search dialog. Search indexing now skips the page description when an identical content record exists, keeping the record with the heading anchor.
Remark LLMs: export a component with output: "function"
With output: "function", _markdown becomes a component instead of a string: Markdown content is still stringified at compile time, while JSX elements stay as JSX, receiving their original props.
Render it with renderToMarkdown from fumadocs-core/server. Elements resolve from props.components: a component can call asMarkdown() to output its own Markdown form, other components (including missing ones) are serialized as JSX syntax.
import { renderToMarkdown } from 'fumadocs-core/server';const { _markdown: Content } = await page.data.load();const text = await renderToMarkdown(<Content components={getMDXComponents()} />);
getText('processed') keeps working: it renders the component for you, with an optional components map:
const text = await page.data.getText('processed', { components: getMDXComponents() });
Supported in bundler collections with both compilers, and in dynamic: true collections & @fumadocs/satteri/local-md with the Sätteri compiler.
fumadocs-core/server: render React trees into Markdown
The Markdown renderer of Fumapress is now part of Fumadocs core. renderToMarkdown() converts RSC output into Markdown, and calling asMarkdown() is how a server component opts in with its own Markdown form:
import { asMarkdown, md, renderToMarkdown } from 'fumadocs-core/server';async function Callout({ title, children }) { if (asMarkdown()) return md.linePrefix('> ')`**${title}**\n${children}`; return <div className="callout">...</div>;}const text = await renderToMarkdown( <Callout title="Note"> <p>Hello</p> </Callout>,);// > **Note**// >// > Hello
Components that never call asMarkdown() are kept as JSX syntax with their serializable props, so are client components, which never run on the server. Host elements returned by an opted-in component are converted with a built-in HTML to Markdown table.
renderRoute() renders a page element only when its component opts in, for giving arbitrary routes a Markdown version. In the browser the module resolves to a stub where asMarkdown() is always false.
Remark LLMs: export a component with output: "function"
With output: "function", _markdown becomes a component instead of a string: Markdown content is still stringified at compile time, while JSX elements stay as JSX, receiving their original props.
Render it with renderToMarkdown from fumadocs-core/server. Elements resolve from props.components: a component can call asMarkdown() to output its own Markdown form, other components (including missing ones) are serialized as JSX syntax.
import { renderToMarkdown } from 'fumadocs-core/server';const { _markdown: Content } = await page.data.load();const text = await renderToMarkdown(<Content components={getMDXComponents()} />);
getText('processed') keeps working: it renders the component for you, with an optional components map:
const text = await page.data.getText('processed', { components: getMDXComponents() });
Supported in bundler collections with both compilers, and in dynamic: true collections & @fumadocs/satteri/local-md with the Sätteri compiler.
Remark LLMs: export a component with output: "function"
With output: "function", _markdown becomes a component instead of a string: Markdown content is still stringified at compile time, while JSX elements stay as JSX, receiving their original props.
Render it with renderToMarkdown from fumadocs-core/server. Elements resolve from props.components: a component can call asMarkdown() to output its own Markdown form, other components (including missing ones) are serialized as JSX syntax.
import { renderToMarkdown } from 'fumadocs-core/server';const { _markdown: Content } = await page.data.load();const text = await renderToMarkdown(<Content components={getMDXComponents()} />);
getText('processed') keeps working: it renders the component for you, with an optional components map:
const text = await page.data.getText('processed', { components: getMDXComponents() });
Supported in bundler collections with both compilers, and in dynamic: true collections & @fumadocs/satteri/local-md with the Sätteri compiler.
Slice Markdown output from the authored source
remarkLlms and the stringify mode of remarkStructure no longer re-stringify the document with mdast-util-to-markdown, they share a stringifier that slices the original source instead. On a 40 kB document with the default preset, remarkLlms went from 45 ms to 11 ms per compile, and structured data with stringify from 34 ms to 8 ms.
For remarkLlms, the output now matches the authored document: heading IDs are appended, frontmatter and ESM nodes are dropped, remarkInclude splices in the included content, and package-manager tabs, images and admonitions appear as written instead of their expanded <Tabs> / <img> / <Callout> forms. Heading levels also no longer lose their # markers. Where generated content replaces the authored form, the output shows the generated content: remarkAutoTypeTable renders its type tables as Markdown tables, instead of the meaningless <auto-type-table> tag.
For remarkStructure, content records keep the authored inline syntax, while links and JSX elements are flattened into their plain text. stringify now takes true or a filterElement callback for the elements whose syntax should be kept:
Elements inserted by plugins (e.g. remarkAutoTypeTable) have no source to slice, kept ones are reconstructed from their attributes so they stay searchable.
The mdast-util-to-markdown based options of both plugins (filterElement variants returning children-only, stringify functions, handlers) are removed, along with the mdast-util-gfm and mdast-util-mdx dependencies. Use the plugins of fumadocs-core if you need custom stringification.
Support HTTP Basic client authentication in OAuth password flow
Some OAuth servers require client credentials in an HTTP Basic Authorization header instead of the request body. The password flow dialog now offers a Client Authentication select to choose between the two methods, as described in RFC 6749, section 2.3.1.
Support HTTP Basic client authentication in OAuth password flow
Some OAuth servers require client credentials in an HTTP Basic Authorization header instead of the request body. The password flow dialog now offers a Client Authentication select to choose between the two methods, as described in RFC 6749, section 2.3.1.