Changelog

The latest releases of Fumadocs.

October 2026

Oct 23
@fumadocs/story@1.5.2
Faster story controls in dev servers

Story files requested together share one TypeScript program, and Vite environments share their results. A cold start with 300 story files takes 4s instead of 30s, without blocking the Vite dev server.

Fix #3742

TypeScript 7.1

Twoslash, type tables and story controls run on the stable API of TypeScript 7.1 (typescript@7.1.0-beta), with code loaded as in-memory files.
- Twoslash no longer writes code blocks to the .twoslash directory, you can remove it from .gitignore.
- Twoslash completions work in the global scope, relative paths in compiler options (like paths) resolve from cwd.
- No tsconfig.fumadocs-typescript.json or tsconfig.fumadocs-story.json is generated.
- Type tables are 2.4x faster on large API references, each from a program of its file and the files it imports.
- The transform option of type tables gets the checker of TypeScript 7.1, typeToString() takes TypeFormatFlags.
Oct 23
@fumadocs/shadcn@0.1.2
Bring your own highlighter

Shiki stays the default, and isn't loaded when you highlight code with another highlighter.
- fumadocs-core/highlight exports a Highlighter interface, created with createHighlights() from fumadocs-core/highlight/highlights (@pierre/highlights) or createShikiHighlighter() from fumadocs-core/highlight/shiki, override() creates one with other options.
- rehypeCodeFromHighlighter from fumadocs-core/mdx-plugins/rehype-code.core highlights code blocks with a highlighter, or a function creating one with the transformers of Fumadocs. createRehypeCode is deprecated, Sätteri has rehypeCodeFromHighlighter in @fumadocs/satteri/rehype-code. Pass transformerTwoslash() in its transformers option to analyze Twoslash blocks in batches.
- createServerCodeBlock() and createDynamicCodeBlock() in Fumadocs UI create code blocks from a highlighter. Dynamic code blocks are highlighted on the server too.
- toJsx() from fumadocs-core/utils/hast-to-jsx converts hast into React elements like toJsxRuntime() of hast-util-to-jsx-runtime, MDX nodes through an evaluator, over 10x faster on highlighted code, whose spans render as one HTML string. Every Fumadocs renderer uses it, hast-util-to-jsx-runtime is no longer a dependency.
- Twoslash loads the languages of code blocks in popups before highlighting, an unknown language there no longer fails the code block.
- OpenAPI Standalone highlights code blocks with Highlights, in its server-rendered pages too.
- The page factories of OpenAPI, GraphQL and AsyncAPI, type tables, createPython(), createPythonComponents(), localHtml() and the shadcn createSnippet() take a highlighter.
- Deprecated shiki and shikiOptions of the API pages and shiki of type tables, pass a highlighter instead.
- Integrations require fumadocs-core 16.17.8, the API pages and shadcn also require fumadocs-ui 16.17.8.
Oct 23
@fumadocs/satteri@0.7.0
Processed Markdown links page-relative images at their served URLs
- Images imported by Remark Image get the URLs bundlers serve them at in Remark LLMs, instead of their relative paths
- Stringifiers output JS expressions with s.expression(), for Markdown only known at runtime
- Search records of included content with images are no longer cut
- The Sätteri preset only imports images in bundlers, at runtime it resolves their sizes like the MDX preset
<include> in Local Markdown

<include> is enabled by default in @fumadocs/local-md and @fumadocs/satteri/local-md, and pages reload when the files they include change, with both the Vite and dev server watchers.
- invalidateFile() returns whether the source uses the file.
- Both require fumadocs-core 16.17.8.
Bring your own highlighter

Shiki stays the default, and isn't loaded when you highlight code with another highlighter.
- fumadocs-core/highlight exports a Highlighter interface, created with createHighlights() from fumadocs-core/highlight/highlights (@pierre/highlights) or createShikiHighlighter() from fumadocs-core/highlight/shiki, override() creates one with other options.
- rehypeCodeFromHighlighter from fumadocs-core/mdx-plugins/rehype-code.core highlights code blocks with a highlighter, or a function creating one with the transformers of Fumadocs. createRehypeCode is deprecated, Sätteri has rehypeCodeFromHighlighter in @fumadocs/satteri/rehype-code. Pass transformerTwoslash() in its transformers option to analyze Twoslash blocks in batches.
- createServerCodeBlock() and createDynamicCodeBlock() in Fumadocs UI create code blocks from a highlighter. Dynamic code blocks are highlighted on the server too.
- toJsx() from fumadocs-core/utils/hast-to-jsx converts hast into React elements like toJsxRuntime() of hast-util-to-jsx-runtime, MDX nodes through an evaluator, over 10x faster on highlighted code, whose spans render as one HTML string. Every Fumadocs renderer uses it, hast-util-to-jsx-runtime is no longer a dependency.
- Twoslash loads the languages of code blocks in popups before highlighting, an unknown language there no longer fails the code block.
- OpenAPI Standalone highlights code blocks with Highlights, in its server-rendered pages too.
- The page factories of OpenAPI, GraphQL and AsyncAPI, type tables, createPython(), createPythonComponents(), localHtml() and the shadcn createSnippet() take a highlighter.
- Deprecated shiki and shikiOptions of the API pages and shiki of type tables, pass a highlighter instead.
- Integrations require fumadocs-core 16.17.8, the API pages and shadcn also require fumadocs-ui 16.17.8.
Oct 23
@fumadocs/openapi-standalone@0.1.2
Bring your own highlighter

Shiki stays the default, and isn't loaded when you highlight code with another highlighter.
- fumadocs-core/highlight exports a Highlighter interface, created with createHighlights() from fumadocs-core/highlight/highlights (@pierre/highlights) or createShikiHighlighter() from fumadocs-core/highlight/shiki, override() creates one with other options.
- rehypeCodeFromHighlighter from fumadocs-core/mdx-plugins/rehype-code.core highlights code blocks with a highlighter, or a function creating one with the transformers of Fumadocs. createRehypeCode is deprecated, Sätteri has rehypeCodeFromHighlighter in @fumadocs/satteri/rehype-code. Pass transformerTwoslash() in its transformers option to analyze Twoslash blocks in batches.
- createServerCodeBlock() and createDynamicCodeBlock() in Fumadocs UI create code blocks from a highlighter. Dynamic code blocks are highlighted on the server too.
- toJsx() from fumadocs-core/utils/hast-to-jsx converts hast into React elements like toJsxRuntime() of hast-util-to-jsx-runtime, MDX nodes through an evaluator, over 10x faster on highlighted code, whose spans render as one HTML string. Every Fumadocs renderer uses it, hast-util-to-jsx-runtime is no longer a dependency.
- Twoslash loads the languages of code blocks in popups before highlighting, an unknown language there no longer fails the code block.
- OpenAPI Standalone highlights code blocks with Highlights, in its server-rendered pages too.
- The page factories of OpenAPI, GraphQL and AsyncAPI, type tables, createPython(), createPythonComponents(), localHtml() and the shadcn createSnippet() take a highlighter.
- Deprecated shiki and shikiOptions of the API pages and shiki of type tables, pass a highlighter instead.
- Integrations require fumadocs-core 16.17.8, the API pages and shadcn also require fumadocs-ui 16.17.8.
Oct 23
@fumadocs/local-md@0.4.0
<include> in Local Markdown

<include> is enabled by default in @fumadocs/local-md and @fumadocs/satteri/local-md, and pages reload when the files they include change, with both the Vite and dev server watchers.
- invalidateFile() returns whether the source uses the file.
- Both require fumadocs-core 16.17.8.
Bring your own highlighter

Shiki stays the default, and isn't loaded when you highlight code with another highlighter.
- fumadocs-core/highlight exports a Highlighter interface, created with createHighlights() from fumadocs-core/highlight/highlights (@pierre/highlights) or createShikiHighlighter() from fumadocs-core/highlight/shiki, override() creates one with other options.
- rehypeCodeFromHighlighter from fumadocs-core/mdx-plugins/rehype-code.core highlights code blocks with a highlighter, or a function creating one with the transformers of Fumadocs. createRehypeCode is deprecated, Sätteri has rehypeCodeFromHighlighter in @fumadocs/satteri/rehype-code. Pass transformerTwoslash() in its transformers option to analyze Twoslash blocks in batches.
- createServerCodeBlock() and createDynamicCodeBlock() in Fumadocs UI create code blocks from a highlighter. Dynamic code blocks are highlighted on the server too.
- toJsx() from fumadocs-core/utils/hast-to-jsx converts hast into React elements like toJsxRuntime() of hast-util-to-jsx-runtime, MDX nodes through an evaluator, over 10x faster on highlighted code, whose spans render as one HTML string. Every Fumadocs renderer uses it, hast-util-to-jsx-runtime is no longer a dependency.
- Twoslash loads the languages of code blocks in popups before highlighting, an unknown language there no longer fails the code block.
- OpenAPI Standalone highlights code blocks with Highlights, in its server-rendered pages too.
- The page factories of OpenAPI, GraphQL and AsyncAPI, type tables, createPython(), createPythonComponents(), localHtml() and the shadcn createSnippet() take a highlighter.
- Deprecated shiki and shikiOptions of the API pages and shiki of type tables, pass a highlighter instead.
- Integrations require fumadocs-core 16.17.8, the API pages and shadcn also require fumadocs-ui 16.17.8.
Oct 23
@fumadocs/local-html@0.2.0
Watch the dependencies of local content
- Integrations call file.addDependency(path) for the files a parsed file depends on, like included files. A change to them invalidates the file, and the Vite & dev server watchers watch them, even outside the content directory.
- invalidateFile() returns whether the source uses the file, onDependency() listens to the dependencies. Custom sources passed to the watchers need both.
- watchWithVite() called after the Vite server started now watches content directories outside of Vite's root.
Unknown languages in Local HTML

Code blocks in languages Shiki doesn't know render as plain text, instead of failing the page.

Bring your own highlighter

Shiki stays the default, and isn't loaded when you highlight code with another highlighter.
- fumadocs-core/highlight exports a Highlighter interface, created with createHighlights() from fumadocs-core/highlight/highlights (@pierre/highlights) or createShikiHighlighter() from fumadocs-core/highlight/shiki, override() creates one with other options.
- rehypeCodeFromHighlighter from fumadocs-core/mdx-plugins/rehype-code.core highlights code blocks with a highlighter, or a function creating one with the transformers of Fumadocs. createRehypeCode is deprecated, Sätteri has rehypeCodeFromHighlighter in @fumadocs/satteri/rehype-code. Pass transformerTwoslash() in its transformers option to analyze Twoslash blocks in batches.
- createServerCodeBlock() and createDynamicCodeBlock() in Fumadocs UI create code blocks from a highlighter. Dynamic code blocks are highlighted on the server too.
- toJsx() from fumadocs-core/utils/hast-to-jsx converts hast into React elements like toJsxRuntime() of hast-util-to-jsx-runtime, MDX nodes through an evaluator, over 10x faster on highlighted code, whose spans render as one HTML string. Every Fumadocs renderer uses it, hast-util-to-jsx-runtime is no longer a dependency.
- Twoslash loads the languages of code blocks in popups before highlighting, an unknown language there no longer fails the code block.
- OpenAPI Standalone highlights code blocks with Highlights, in its server-rendered pages too.
- The page factories of OpenAPI, GraphQL and AsyncAPI, type tables, createPython(), createPythonComponents(), localHtml() and the shadcn createSnippet() take a highlighter.
- Deprecated shiki and shikiOptions of the API pages and shiki of type tables, pass a highlighter instead.
- Integrations require fumadocs-core 16.17.8, the API pages and shadcn also require fumadocs-ui 16.17.8.
Oct 23
@fumadocs/local-content@0.3.0
Watch the dependencies of local content
- Integrations call file.addDependency(path) for the files a parsed file depends on, like included files. A change to them invalidates the file, and the Vite & dev server watchers watch them, even outside the content directory.
- invalidateFile() returns whether the source uses the file, onDependency() listens to the dependencies. Custom sources passed to the watchers need both.
- watchWithVite() called after the Vite server started now watches content directories outside of Vite's root.
Oct 23
@fumadocs/json-schema@0.3.5
Schema UI links through unions

Copied property links restore the selected oneOf/anyOf members and the schemas opened from them again, instead of staying at the root.

Fix #3732
Oct 23
@fumadocs/graphql@0.4.2
Bring your own highlighter

Shiki stays the default, and isn't loaded when you highlight code with another highlighter.
- fumadocs-core/highlight exports a Highlighter interface, created with createHighlights() from fumadocs-core/highlight/highlights (@pierre/highlights) or createShikiHighlighter() from fumadocs-core/highlight/shiki, override() creates one with other options.
- rehypeCodeFromHighlighter from fumadocs-core/mdx-plugins/rehype-code.core highlights code blocks with a highlighter, or a function creating one with the transformers of Fumadocs. createRehypeCode is deprecated, Sätteri has rehypeCodeFromHighlighter in @fumadocs/satteri/rehype-code. Pass transformerTwoslash() in its transformers option to analyze Twoslash blocks in batches.
- createServerCodeBlock() and createDynamicCodeBlock() in Fumadocs UI create code blocks from a highlighter. Dynamic code blocks are highlighted on the server too.
- toJsx() from fumadocs-core/utils/hast-to-jsx converts hast into React elements like toJsxRuntime() of hast-util-to-jsx-runtime, MDX nodes through an evaluator, over 10x faster on highlighted code, whose spans render as one HTML string. Every Fumadocs renderer uses it, hast-util-to-jsx-runtime is no longer a dependency.
- Twoslash loads the languages of code blocks in popups before highlighting, an unknown language there no longer fails the code block.
- OpenAPI Standalone highlights code blocks with Highlights, in its server-rendered pages too.
- The page factories of OpenAPI, GraphQL and AsyncAPI, type tables, createPython(), createPythonComponents(), localHtml() and the shadcn createSnippet() take a highlighter.
- Deprecated shiki and shikiOptions of the API pages and shiki of type tables, pass a highlighter instead.
- Integrations require fumadocs-core 16.17.8, the API pages and shadcn also require fumadocs-ui 16.17.8.
Oct 23
@fumadocs/asyncapi@0.5.3
Bring your own highlighter

Shiki stays the default, and isn't loaded when you highlight code with another highlighter.
- fumadocs-core/highlight exports a Highlighter interface, created with createHighlights() from fumadocs-core/highlight/highlights (@pierre/highlights) or createShikiHighlighter() from fumadocs-core/highlight/shiki, override() creates one with other options.
- rehypeCodeFromHighlighter from fumadocs-core/mdx-plugins/rehype-code.core highlights code blocks with a highlighter, or a function creating one with the transformers of Fumadocs. createRehypeCode is deprecated, Sätteri has rehypeCodeFromHighlighter in @fumadocs/satteri/rehype-code. Pass transformerTwoslash() in its transformers option to analyze Twoslash blocks in batches.
- createServerCodeBlock() and createDynamicCodeBlock() in Fumadocs UI create code blocks from a highlighter. Dynamic code blocks are highlighted on the server too.
- toJsx() from fumadocs-core/utils/hast-to-jsx converts hast into React elements like toJsxRuntime() of hast-util-to-jsx-runtime, MDX nodes through an evaluator, over 10x faster on highlighted code, whose spans render as one HTML string. Every Fumadocs renderer uses it, hast-util-to-jsx-runtime is no longer a dependency.
- Twoslash loads the languages of code blocks in popups before highlighting, an unknown language there no longer fails the code block.
- OpenAPI Standalone highlights code blocks with Highlights, in its server-rendered pages too.
- The page factories of OpenAPI, GraphQL and AsyncAPI, type tables, createPython(), createPythonComponents(), localHtml() and the shadcn createSnippet() take a highlighter.
- Deprecated shiki and shikiOptions of the API pages and shiki of type tables, pass a highlighter instead.
- Integrations require fumadocs-core 16.17.8, the API pages and shadcn also require fumadocs-ui 16.17.8.
Oct 23
@fumadocs/ai-chat@0.1.2
Bring your own highlighter

Shiki stays the default, and isn't loaded when you highlight code with another highlighter.
- fumadocs-core/highlight exports a Highlighter interface, created with createHighlights() from fumadocs-core/highlight/highlights (@pierre/highlights) or createShikiHighlighter() from fumadocs-core/highlight/shiki, override() creates one with other options.
- rehypeCodeFromHighlighter from fumadocs-core/mdx-plugins/rehype-code.core highlights code blocks with a highlighter, or a function creating one with the transformers of Fumadocs. createRehypeCode is deprecated, Sätteri has rehypeCodeFromHighlighter in @fumadocs/satteri/rehype-code. Pass transformerTwoslash() in its transformers option to analyze Twoslash blocks in batches.
- createServerCodeBlock() and createDynamicCodeBlock() in Fumadocs UI create code blocks from a highlighter. Dynamic code blocks are highlighted on the server too.
- toJsx() from fumadocs-core/utils/hast-to-jsx converts hast into React elements like toJsxRuntime() of hast-util-to-jsx-runtime, MDX nodes through an evaluator, over 10x faster on highlighted code, whose spans render as one HTML string. Every Fumadocs renderer uses it, hast-util-to-jsx-runtime is no longer a dependency.
- Twoslash loads the languages of code blocks in popups before highlighting, an unknown language there no longer fails the code block.
- OpenAPI Standalone highlights code blocks with Highlights, in its server-rendered pages too.
- The page factories of OpenAPI, GraphQL and AsyncAPI, type tables, createPython(), createPythonComponents(), localHtml() and the shadcn createSnippet() take a highlighter.
- Deprecated shiki and shikiOptions of the API pages and shiki of type tables, pass a highlighter instead.
- Integrations require fumadocs-core 16.17.8, the API pages and shadcn also require fumadocs-ui 16.17.8.
Oct 20
fumadocs-twoslash@4.0.3
Hover signatures of repeated calls

Hovering a call shows that call's own resolved signature again. Repeated calls of the same function, such as two z.enum([...]) calls with different values, all showed the first call's signature, since the hover cache did not tell call sites apart.

Fix #3727
Oct 20
fumadocs-preview@0.2.4
AI chat prompt as instructions

Pass the AI chat system prompt as instructions, replacing the system option deprecated in AI SDK 7.
Oct 20
fumadocs-openapi@12.5.4
Load documents once
- includeDocument: false of createOpenAPI() and createAsyncAPI() leaves documents out of page props, pages load each one once per browser session with loadDocument of createOpenAPIPage() and createAsyncAPIPage().
- Same for GraphQL schemas: includeSchema: false of createGraphQL() with loadSchema of createGraphQLPage().
Oct 20
fumadocs-mdx@15.4.9
Turbopack loader warnings
- Next.js 16.4 builds no longer warn Module not found: Can't resolve <dynamic> for the config imports of the loaders.
Oct 20
create-fumadocs-app@16.2.25
Published create-fumadocs-app@16.2.25.
Oct 20
@fumadocs/graphql@0.4.1
Load documents once
- includeDocument: false of createOpenAPI() and createAsyncAPI() leaves documents out of page props, pages load each one once per browser session with loadDocument of createOpenAPIPage() and createAsyncAPIPage().
- Same for GraphQL schemas: includeSchema: false of createGraphQL() with loadSchema of createGraphQLPage().
Oct 20
@fumadocs/asyncapi@0.5.2
Load documents once
- includeDocument: false of createOpenAPI() and createAsyncAPI() leaves documents out of page props, pages load each one once per browser session with loadDocument of createOpenAPIPage() and createAsyncAPIPage().
- Same for GraphQL schemas: includeSchema: false of createGraphQL() with loadSchema of createGraphQLPage().
Oct 19
fumadocs@16.17.7
- @fumadocs/base-ui@16.17.7
- fumadocs-core@16.17.7
- fumadocs-ui@16.17.7
Imports across Windows drives
- remarkImage and generated .source files import files on another drive or a UNC path by their absolute path.
- Generated imports of files in dot-folders are prefixed with ./.
Fix #3723
Oct 19
fumadocs-mdx@15.4.8
Imports across Windows drives
- remarkImage and generated .source files import files on another drive or a UNC path by their absolute path.
- Generated imports of files in dot-folders are prefixed with ./.
Fix #3723
Oct 19
create-fumadocs-app@16.2.24
Published create-fumadocs-app@16.2.24.
Oct 19
@fumadocs/satteri@0.6.2
Imports across Windows drives
- remarkImage and generated .source files import files on another drive or a UNC path by their absolute path.
- Generated imports of files in dot-folders are prefixed with ./.
Fix #3723
Oct 19
@fumadocs/json-schema@0.3.4
Recursive schemas in mergeAllOf()
- Recursive schemas no longer overflow, e.g. subtypes that extend a parent listing them in oneOf merge to the parent's keywords and their own.
- Nested schemas defined by multiple members, like a property, are combined with allOf and merged when read.
- Keywords of a composed schema win over its members, including readOnly and writeOnly.
Fix #3724
Oct 19
fumadocs-openapi@12.5.3
Smaller bundles
- fumadocs-openapi/ui/base and createOpenAPIBaseRenderer() no longer bundle the full Shiki bundle.
Fix #3714

Code samples
- Bodies with quotes, line breaks, NUL, BOM or bidi characters produce valid Python, Java, Go, Rust, JavaScript and C# samples that send them exactly.
- Go and Rust samples no longer indent the lines of multi-line bodies.
- text/plain bodies are sent as written, in samples and the playground.
- cURL samples send JSON bodies of +json and ; charset= media types as JSON.
Example cards with code block title bars
- Example cards put their controls in the title bar of their code block, next to its copy button, so code no longer runs under the button on narrow screens.
- Selects with a single option, like one status code, show a plain label.
- The playground button follows the corner radius of the bar around it.
Tag hierarchy in per: 'tag'
- Pages follow the OpenAPI 3.2 tag hierarchy, in the folder of their parent tag.
- Tags without operations or with a kind other than nav get no page.
- Undeclared tags get pages too, untagged operations are listed in unknown.
- Index cards of generateFiles() include pages in folders.
Fix #3719

Generated pages in every language
- Virtual files accept a locale, $ for every language, instead of parsing it from their path.
- Pages from staticSource() and dynamicSource() of OpenAPI, AsyncAPI and GraphQL are shared with every language of loader().
Fix #3720
Oct 19
@fumadocs/json-schema@0.3.3
Info tags that open schemas
- An InfoTag with open: { name, $ref } opens the schema $ref in Schema UI, like the type of a property.
Oct 19
fumadocs@16.17.6
- @fumadocs/base-ui@16.17.6
- fumadocs-core@16.17.6
- fumadocs-ui@16.17.6
i18n parser: 'none'
- parser: 'none' no longer parses locales from file paths, files without a locale belong to the default language.
Generated pages in every language
- Virtual files accept a locale, $ for every language, instead of parsing it from their path.
- Pages from staticSource() and dynamicSource() of OpenAPI, AsyncAPI and GraphQL are shared with every language of loader().
Fix #3720
Oct 19
create-fumadocs-app@16.2.23
Published create-fumadocs-app@16.2.23.

Oct 19

@fumadocs/language@0.2.16

Redesigned GraphQL pages

Operation pages start with their signature and directives, like QUERY customer(id: ID!): Customer, and keep the types they use in place: arguments and return types open in Schema UI panels.
Pages of named types are opt-in with includeTypes, they show the SDL of types and where they are used.
Example requests and responses beside operations, with a select of examples and code samples in cURL, JavaScript, Go, Python, Java, C# and Rust.
Named examples from GraphQL documents with the examples option of createGraphQL().
The playground opens in a dialog: an editor with validation and formatting, variables as a form or JSON, headers, and responses with their GraphQL errors.
The playground runs subscriptions over graphql-ws or GraphQL over SSE (subscriptionUrl), and logs their events.
Directives applied in the schema show their definitions, @oneOf input objects are supported.
getText() returns pages in Markdown for LLMs, operations with the SDL of types they use.
Chinese translations of GraphQL pages in @fumadocs/language.

API changes

Before	Now
pages of named types by default	`includeTypes: true`, also for `per: 'file'`
`useOperation().example`	`examples`, with `selected` and `select()`
`slots.relations` and `slots.scalar` of `renderTypeLayout`	`slots.definition`, `usages` and `sdl`
`@fumadocs/graphql/utils/snippets`	the `codeUsages` option
`inputTypeToJsonSchema(type, depth)`	`inputTypeToJsonSchema(type)`, recursive inputs are shared
`slots.directives` of `renderOperationLayout` and `renderTypeLayout`	in `slots.playground` and `slots.definition`
`renderArguments` of `generateGraphQLSchemaUI()`, `SchemaViewRoot.args`	arguments open in their own panel

Added createCodeUsageGeneratorRegistry() and registerDefaultCodeUsages() to @fumadocs/graphql/ui.
Added usePlayground(), useRequestValues() and subscribeGraphQL() to @fumadocs/graphql/playground, the installed playground runs on them.
Removed HeaderItem, filterHeaderItems(), readStored(), writeStored(), getEndpointOrigin() and syncOperationVariables() from @fumadocs/graphql/playground, usePlayground() keeps headers by endpoint origin.
Added relations.unions to useNamedType().
The Schema UI root also takes a schema coordinate, like Query.orders() for the arguments of Query.orders.

Oct 19

@fumadocs/graphql@0.4.0

Redesigned GraphQL pages

Operation pages start with their signature and directives, like QUERY customer(id: ID!): Customer, and keep the types they use in place: arguments and return types open in Schema UI panels.
Pages of named types are opt-in with includeTypes, they show the SDL of types and where they are used.
Example requests and responses beside operations, with a select of examples and code samples in cURL, JavaScript, Go, Python, Java, C# and Rust.
Named examples from GraphQL documents with the examples option of createGraphQL().
The playground opens in a dialog: an editor with validation and formatting, variables as a form or JSON, headers, and responses with their GraphQL errors.
The playground runs subscriptions over graphql-ws or GraphQL over SSE (subscriptionUrl), and logs their events.
Directives applied in the schema show their definitions, @oneOf input objects are supported.
getText() returns pages in Markdown for LLMs, operations with the SDL of types they use.
Chinese translations of GraphQL pages in @fumadocs/language.

API changes

Before	Now
pages of named types by default	`includeTypes: true`, also for `per: 'file'`
`useOperation().example`	`examples`, with `selected` and `select()`
`slots.relations` and `slots.scalar` of `renderTypeLayout`	`slots.definition`, `usages` and `sdl`
`@fumadocs/graphql/utils/snippets`	the `codeUsages` option
`inputTypeToJsonSchema(type, depth)`	`inputTypeToJsonSchema(type)`, recursive inputs are shared
`slots.directives` of `renderOperationLayout` and `renderTypeLayout`	in `slots.playground` and `slots.definition`
`renderArguments` of `generateGraphQLSchemaUI()`, `SchemaViewRoot.args`	arguments open in their own panel

Added createCodeUsageGeneratorRegistry() and registerDefaultCodeUsages() to @fumadocs/graphql/ui.
Added usePlayground(), useRequestValues() and subscribeGraphQL() to @fumadocs/graphql/playground, the installed playground runs on them.
Removed HeaderItem, filterHeaderItems(), readStored(), writeStored(), getEndpointOrigin() and syncOperationVariables() from @fumadocs/graphql/playground, usePlayground() keeps headers by endpoint origin.
Added relations.unions to useNamedType().
The Schema UI root also takes a schema coordinate, like Query.orders() for the arguments of Query.orders.

Generated pages in every language

Virtual files accept a locale, $ for every language, instead of parsing it from their path.
Pages from staticSource() and dynamicSource() of OpenAPI, AsyncAPI and GraphQL are shared with every language of loader().

Fix #3720

Oct 19
@fumadocs/asyncapi@0.5.1
TypeScript definitions on copy
- Message schemas generate their TypeScript definitions when the button copies them, not on every render.
Example cards with code block title bars
- Example cards put their controls in the title bar of their code block, next to its copy button, so code no longer runs under the button on narrow screens.
- Selects with a single option, like one status code, show a plain label.
- The playground button follows the corner radius of the bar around it.
Generated pages in every language
- Virtual files accept a locale, $ for every language, instead of parsing it from their path.
- Pages from staticSource() and dynamicSource() of OpenAPI, AsyncAPI and GraphQL are shared with every language of loader().
Fix #3720

Changelog

October 2026

Faster story controls in dev servers

TypeScript 7.1

Bring your own highlighter

Processed Markdown links page-relative images at their served URLs

<include> in Local Markdown

Bring your own highlighter

Bring your own highlighter

<include> in Local Markdown

Bring your own highlighter

Watch the dependencies of local content

Unknown languages in Local HTML

Bring your own highlighter

Watch the dependencies of local content

Schema UI links through unions

Bring your own highlighter

Bring your own highlighter

Bring your own highlighter

Hover signatures of repeated calls

AI chat prompt as instructions

Load documents once

Turbopack loader warnings

Load documents once

Load documents once

Imports across Windows drives

Imports across Windows drives

Imports across Windows drives

Recursive schemas in mergeAllOf()

Smaller bundles

Code samples

Example cards with code block title bars

Tag hierarchy in per: 'tag'

Generated pages in every language

Info tags that open schemas

i18n parser: 'none'

Generated pages in every language

Redesigned GraphQL pages

API changes

Redesigned GraphQL pages

API changes

Generated pages in every language

TypeScript definitions on copy

Example cards with code block title bars

Generated pages in every language

Faster story controls in dev servers

TypeScript 7.1

Bring your own highlighter

Processed Markdown links page-relative images at their served URLs

<include> in Local Markdown

Bring your own highlighter

Bring your own highlighter

<include> in Local Markdown

Bring your own highlighter

Watch the dependencies of local content

Unknown languages in Local HTML

Bring your own highlighter

Watch the dependencies of local content

Bring your own highlighter

Bring your own highlighter

Bring your own highlighter

Load documents once

Load documents once

Load documents once

Imports across Windows drives

Recursive schemas in mergeAllOf()

Smaller bundles

Code samples

Example cards with code block title bars

Tag hierarchy in per: 'tag'

Generated pages in every language

i18n parser: 'none'

Generated pages in every language

Redesigned GraphQL pages

API changes

Redesigned GraphQL pages

API changes

Generated pages in every language

TypeScript definitions on copy

Example cards with code block title bars

`<include>` in Local Markdown

`<include>` in Local Markdown

AI chat prompt as `instructions`

Recursive schemas in `mergeAllOf()`

Tag hierarchy in `per: 'tag'`

i18n `parser: 'none'`

`<include>` in Local Markdown

`<include>` in Local Markdown

Recursive schemas in `mergeAllOf()`

Tag hierarchy in `per: 'tag'`

i18n `parser: 'none'`