The playground installed by npx @fumadocs/cli add openapi/playground imported useAuthFields, requestOAuthToken and their types from fumadocs-openapi/playground, which did not export them. They are now exported.
With a warm build cache, ?only=frontmatter imports were served the fully compiled page from cache instead of the frontmatter module, so every page was bundled two more times. The cache now only applies to full compilations.
All packages now declare sideEffects in package.json, so bundlers can tree-shake unused modules. Packages shipping stylesheets list them as side effects to keep CSS imports.
All packages now declare sideEffects in package.json, so bundlers can tree-shake unused modules. Packages shipping stylesheets list them as side effects to keep CSS imports.
All packages now declare sideEffects in package.json, so bundlers can tree-shake unused modules. Packages shipping stylesheets list them as side effects to keep CSS imports.
All packages now declare sideEffects in package.json, so bundlers can tree-shake unused modules. Packages shipping stylesheets list them as side effects to keep CSS imports.
All packages now declare sideEffects in package.json, so bundlers can tree-shake unused modules. Packages shipping stylesheets list them as side effects to keep CSS imports.
All packages now declare sideEffects in package.json, so bundlers can tree-shake unused modules. Packages shipping stylesheets list them as side effects to keep CSS imports.
All packages now declare sideEffects in package.json, so bundlers can tree-shake unused modules. Packages shipping stylesheets list them as side effects to keep CSS imports.
All packages now declare sideEffects in package.json, so bundlers can tree-shake unused modules. Packages shipping stylesheets list them as side effects to keep CSS imports.
All packages now declare sideEffects in package.json, so bundlers can tree-shake unused modules. Packages shipping stylesheets list them as side effects to keep CSS imports.
All packages now declare sideEffects in package.json, so bundlers can tree-shake unused modules. Packages shipping stylesheets list them as side effects to keep CSS imports.
All packages now declare sideEffects in package.json, so bundlers can tree-shake unused modules. Packages shipping stylesheets list them as side effects to keep CSS imports.
All packages now declare sideEffects in package.json, so bundlers can tree-shake unused modules. Packages shipping stylesheets list them as side effects to keep CSS imports.
All packages now declare sideEffects in package.json, so bundlers can tree-shake unused modules. Packages shipping stylesheets list them as side effects to keep CSS imports.
All packages now declare sideEffects in package.json, so bundlers can tree-shake unused modules. Packages shipping stylesheets list them as side effects to keep CSS imports.
New registry format
The CLI is upgraded to Fuma CLI 0.3, the registry is now a manifest with the raw files instead of one JSON per component.
Installing fetches every needed file in parallel, and no longer parses the installed files to link their imports.
Layouts are imported from fumadocs-ui unless you have installed them, without a Fumadocs-specific plugin.
Older versions of the CLI cannot read the new registry, upgrade to install components.
Moved files
Some components are installed to a location that follows their source, update your imports if you install them again:
Slots are named after their path, like layouts/docs/slots/sidebar instead of slots/docs/sidebar. fumadocs customise is unchanged.
Shorter names for integration components
The components of integrations dropped their fumadocs/ prefix:
npx @fumadocs/cli add openapi/page
Before
Now
fumadocs/openapi/*
openapi/*
fumadocs/asyncapi/*
asyncapi/*
fumadocs/graphql/*
graphql/*
fumadocs/story/*
story/*
fumadocs/sanity/*
sanity/*
fumadocs/api-docs/*
api-docs/*
The old names are gone, update the commands in your scripts. fumadocs/base-ui and fumadocs/radix-ui are unchanged, the CLI resolves them from your configured uiLibrary.
@fumadocs/base-ui@16.15.12
fumadocs-core@16.15.12
fumadocs-ui@16.15.12
Fix filterElement being ignored by remarkLLMs
remarkLLMs wrote its own filterElement over yours, so the option did nothing:
remarkLLMs({ // never ran filterElement: (node) => node.name !== 'Callout',});
Your function now runs for every node except mdxjsEsm, which stays excluded either way.
Fumadocs MDX passes this option through postprocess.includeProcessedMarkdown.
Headless API pages
API pages are now built on a headless layer, use it to build your own UI:
fumadocs-openapi: createOpenAPIRenderer() with your own components, and the hooks of a page: useOpenAPI(), useComponents(), useServer() and useRenderContext(). createOpenAPIBaseRenderer() is the same with nothing built in: pass shiki, codeUsages and generateTypeScriptDefinitions yourself.
fumadocs-openapi/operation: <OperationProvider /> and the hooks of an operation, like useOperation() and useExampleRequests().
fumadocs-openapi/playground: useAuthFields() turns the security requirements of an operation into form fields, the ones the API playground renders and encodes into request data. requestOAuthToken() runs an OAuth flow of a security scheme.
the Schema UI, installed with npx @fumadocs/cli add fumadocs/api-docs/schema: its generation and navigation state (generateSchemaUI(), useSchemaTabs()) come with the copy.
useServer() also resolves the URL of a request: resolveUrl(pathname) fills in the variables of the selected server, against the page origin.
Code samples from x-codeSamples and generateCodeSamples are now rendered when their id isn't a built-in generator.
Data info tags in Schema UI
SchemaData.infoTags entries are data rendered by the UI: { label, value, block? } or { label, list }. Custom nodes ({ node }) are still accepted, code reading tag.node must handle all shapes.
playground.provider is removed, the page provides the auth state of API 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 fumadocs/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: playground.render becomes () => <PlaygroundClient writeOnly readOnly={false} />.
The ctx of content render options is the render options of the page, what useRenderContext() returns: shiki, content, playground, showResponseSchema and schemaUI. ctx.schema, ctx.SchemaUI and ctx._default_processMarkdown are removed, read the document from useOpenAPI().doc and the components from useComponents().
Migrate hooks
The hooks of fumadocs-openapi/ui are replaced by the headless ones:
v11
v12
useRenderContext()
useOpenAPI() (schema is renamed to doc), useComponents(), and useRenderContext() for the render options only
useServerContext()
useServer()
useOperationContext()
useOperation(), useExampleRequests(), useExampleRequest() (on /operation)
- 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();
Components installed from v11 with Fumadocs CLI (e.g. the API playground) use the old hooks, reinstall them.
Remove deprecated APIs
Removed
Use
fumadocs-openapi/ui/create-client
createOpenAPIPage() from fumadocs-openapi/ui
ApiPageProps
OpenAPIPageProps
OperationItem and WebhookItem of fumadocs-openapi/ui
import them from fumadocs-openapi
getAPIPageProps() and getClientAPIPageProps()
getOpenAPIPageProps()
defineI18nOpenAPI()
i18n.translations().extend(openapiTranslations())
APIPage of MDX components
OpenAPIPage, generated files only render it
Moved exports
Everything that renders sits under /ui:
Was
Now
fumadocs-openapi/playground/client
fumadocs-openapi/ui/playground/client
fumadocs-openapi/scalar
fumadocs-openapi/ui/scalar
GenerateTypeScriptDefinitionsContext now comes from the package entry, next to the runtime option it types.
Client-safe package entry
generateFiles() reads and writes files, so the package entry ships a stubbed build under the browser condition. Client components can import createOpenAPIRenderer() and the hooks without pulling node:fs into the bundle.
Default page components
createOpenAPIRenderer(), createAsyncAPIRenderer() and createGraphQLRenderer() fill the Markdown, CodeBlock and Heading components you didn't pass, rendering Markdown through Remark and code blocks through Shiki:
Select and Input follow the Shadcn UI API, so a project that already has them keeps its own. @fumadocs/story no longer ships a second copy of either.
labelVariants moved to the installed label component, leaving the input a plain Shadcn-compatible primitive.
The integrations share one implementation of these internally, instead of each keeping a copy: the selected server and its variables, the state of an async request, the coloured label of methods and kinds, and the plain-object check of both schema layers.
The request pipeline of the playground stays in the package too, so an installed playground drives it instead of copying it: encodeRequestData(), resolveMediaAdapter(), isMediaTypeSupported() and the request data types come from fumadocs-openapi/requests, and createBrowserFetcher() with usePlaygroundAuth() from fumadocs-openapi/playground.
@fumadocs/json-schema
The JSON Schema utilities of API pages are now 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 renders a schema into the data an API page draws: generateSchemaUI() with the SchemaData and InfoTag types. It was in the Schema UI before, where every install copied it. A labelled tag can be prose, for values like a Markdown deprecation reason.
They were @fumadocs/api-docs/schema/* before, and the API was cleaned up while moving:
Before
Now
ParsedSchema
JsonSchema
NoReference / NoReferenceSwallow
Dereferenced / DereferencedShallow
dereferenceShallow(schema)
dereference(schema)
matchesSchema(schema, value)
matches(schema, value)
typeMatches(value, type)
matchesType(value, type)
schemaToString(schema, FormatFlags.UseAlias)
stringify(schema, { alias: true })
Trim code usages and TypeScript definitions
createOpenAPIBaseRenderer() from fumadocs-openapi registers no code usage generators and no TypeScript definitions, so a page built on it bundles only what you pass:
import { createCodeUsageGeneratorRegistry } from 'fumadocs-openapi/requests/generators';import { curl } from 'fumadocs-openapi/requests/generators/curl';createOpenAPIBaseRenderer({ shiki, codeUsages: createCodeUsageGeneratorRegistry().register(curl), components: { ... },});
createOpenAPIRenderer() and fumadocs-openapi/ui register every language and TypeScript definitions for you.
Remove useStorageKey()
The hook returned (name) => storageKeyPrefix + name. Read the prefix from the page instead:
It held the UI the integrations share, and that UI is now either bundled into them or installed with Fumadocs CLI, so nothing imports it by name any more. If you imported it directly:
Before
Now
@fumadocs/api-docs/schema/*
@fumadocs/json-schema
@fumadocs/api-docs/components/schema*
npx @fumadocs/cli add fumadocs/api-docs/schema
@fumadocs/api-docs/components/* (the UI)
installed with the component that uses it
@fumadocs/api-docs/i18n
the integration's own Translations covers its keys
@fumadocs/api-docs/css/preset.css
already included by the integration's preset
The CLI namespace is unchanged, fumadocs/api-docs/schema still installs the Schema UI.
This exported _mdast with no value, and getMDAST() then reported that includeMDAST was disabled. removePosition strips positions in place and returns nothing, so JSON.stringify received undefined.
The tree is now cloned, stripped, and serialized from the clone.
Fix SOURCEMAP_BROKEN warnings on Vite
With build.sourcemap enabled, Vite warned once per content and meta file because the loaders returned no source map. They now return an empty map when nothing is generated.
Source maps for MDX stay opt-in, pass SourceMapGenerator from source-map to MDX options:
createOpenAPIRenderer(), createAsyncAPIRenderer() and createGraphQLRenderer() fill the Markdown, CodeBlock and Heading components you didn't pass, rendering Markdown through Remark and code blocks through Shiki:
Select and Input follow the Shadcn UI API, so a project that already has them keeps its own. @fumadocs/story no longer ships a second copy of either.
labelVariants moved to the installed label component, leaving the input a plain Shadcn-compatible primitive.
The integrations share one implementation of these internally, instead of each keeping a copy: the selected server and its variables, the state of an async request, the coloured label of methods and kinds, and the plain-object check of both schema layers.
The request pipeline of the playground stays in the package too, so an installed playground drives it instead of copying it: encodeRequestData(), resolveMediaAdapter(), isMediaTypeSupported() and the request data types come from fumadocs-openapi/requests, and createBrowserFetcher() with usePlaygroundAuth() from fumadocs-openapi/playground.
Replace the UI of stories
The control panel is no longer fixed, defineStoryFactory() takes your own:
lib/story.tsx
import { defineStoryFactory } from '@fumadocs/story/vite/client';import { WithControl } from '@/components/story';export const { defineStory } = defineStoryFactory({ WithControl });
Install the built-in one and edit it:
npx @fumadocs/cli add fumadocs/story/controls
Or build your own on @fumadocs/story: <StoryProvider /> holds the selected variant and the form engine, useStory() exposes the presets and useStoryArgs() the arguments of the rendered component.
The entry ships a stubbed build under the browser condition, so client components can import them without pulling the story factory's Node dependencies. @fumadocs/story/type-tree does the same: collapse() is stubbed under the browser condition, so the installed controls import the sampler, stringifier and validator from it.
The control of a union prop validated the field against the index of each branch, so it picked an arbitrary one. It now validates against the current value, falling back to the first branch.
validate() from @fumadocs/story/type-tree also rejected null for null nodes, it compared against the string 'null'.
@fumadocs/json-schema
The JSON Schema utilities of API pages are now 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 renders a schema into the data an API page draws: generateSchemaUI() with the SchemaData and InfoTag types. It was in the Schema UI before, where every install copied it. A labelled tag can be prose, for values like a Markdown deprecation reason.
They were @fumadocs/api-docs/schema/* before, and the API was cleaned up while moving:
Before
Now
ParsedSchema
JsonSchema
NoReference / NoReferenceSwallow
Dereferenced / DereferencedShallow
dereferenceShallow(schema)
dereference(schema)
matchesSchema(schema, value)
matches(schema, value)
typeMatches(value, type)
matchesType(value, type)
schemaToString(schema, FormatFlags.UseAlias)
stringify(schema, { alias: true })
Trim code usages and TypeScript definitions
createOpenAPIBaseRenderer() from fumadocs-openapi registers no code usage generators and no TypeScript definitions, so a page built on it bundles only what you pass:
import { createCodeUsageGeneratorRegistry } from 'fumadocs-openapi/requests/generators';import { curl } from 'fumadocs-openapi/requests/generators/curl';createOpenAPIBaseRenderer({ shiki, codeUsages: createCodeUsageGeneratorRegistry().register(curl), components: { ... },});
createOpenAPIRenderer() and fumadocs-openapi/ui register every language and TypeScript definitions for you.
Remove useStorageKey()
The hook returned (name) => storageKeyPrefix + name. Read the prefix from the page instead:
It held the UI the integrations share, and that UI is now either bundled into them or installed with Fumadocs CLI, so nothing imports it by name any more. If you imported it directly:
Before
Now
@fumadocs/api-docs/schema/*
@fumadocs/json-schema
@fumadocs/api-docs/components/schema*
npx @fumadocs/cli add fumadocs/api-docs/schema
@fumadocs/api-docs/components/* (the UI)
installed with the component that uses it
@fumadocs/api-docs/i18n
the integration's own Translations covers its keys
@fumadocs/api-docs/css/preset.css
already included by the integration's preset
The CLI namespace is unchanged, fumadocs/api-docs/schema still installs the Schema UI.
Headless layer
GraphQL pages are now built on a headless layer, use it to build your own UI:
<GraphQLProvider /> holds the schema built from SDL, the page links and your components.
<OperationProvider /> and useOperation() derive an operation: its field, title, directives and generated example.
<TypeProvider /> and useNamedType() derive a named type: its kind, directives, relations and usages.
useGraphQL(), useComponents(), useRenderContext(), useTypeLink() and useOperationLink() expose the page state.
generateRequestSnippets() from @fumadocs/graphql/utils/snippets builds the cURL and fetch snippets of an example.
generateGraphQLSchemaUI() turns a type, field or argument into the data the Schema UI draws, the installed Schema UI only renders it.
@fumadocs/graphql/ui is built on it, its rendering is unchanged. typeLinks and operationLinks receive the name (and kind) only, the ctx argument is gone.
Install the UI
The UI of GraphQL pages can be installed with Fumadocs CLI and edited:
npx @fumadocs/cli add fumadocs/graphql/page
It installs <GraphQLPage /> itself, import it from @/components/graphql/page in place of your components/api-page.tsx.
Parts are installable too (operation, type-docs, schema-ui, playground) and passed to the new components options:
The playground is its own entry, so installing the operation or page UI no longer copies it:
npx @fumadocs/cli add fumadocs/graphql/playground
What it runs on comes from @fumadocs/graphql/playground: executeGraphQL() (moved from the package entry), inputTypeToJsonSchema() for the form model of arguments, and the stored endpoint and headers.
Highlighting out of the box
createGraphQLRenderer() highlights code blocks with the full Shiki bundle, pass a smaller shiki factory to trim it.
Default page components
createOpenAPIRenderer(), createAsyncAPIRenderer() and createGraphQLRenderer() fill the Markdown, CodeBlock and Heading components you didn't pass, rendering Markdown through Remark and code blocks through Shiki:
Select and Input follow the Shadcn UI API, so a project that already has them keeps its own. @fumadocs/story no longer ships a second copy of either.
labelVariants moved to the installed label component, leaving the input a plain Shadcn-compatible primitive.
The integrations share one implementation of these internally, instead of each keeping a copy: the selected server and its variables, the state of an async request, the coloured label of methods and kinds, and the plain-object check of both schema layers.
The request pipeline of the playground stays in the package too, so an installed playground drives it instead of copying it: encodeRequestData(), resolveMediaAdapter(), isMediaTypeSupported() and the request data types come from fumadocs-openapi/requests, and createBrowserFetcher() with usePlaygroundAuth() from fumadocs-openapi/playground.
@fumadocs/json-schema
The JSON Schema utilities of API pages are now 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 renders a schema into the data an API page draws: generateSchemaUI() with the SchemaData and InfoTag types. It was in the Schema UI before, where every install copied it. A labelled tag can be prose, for values like a Markdown deprecation reason.
They were @fumadocs/api-docs/schema/* before, and the API was cleaned up while moving:
Before
Now
ParsedSchema
JsonSchema
NoReference / NoReferenceSwallow
Dereferenced / DereferencedShallow
dereferenceShallow(schema)
dereference(schema)
matchesSchema(schema, value)
matches(schema, value)
typeMatches(value, type)
matchesType(value, type)
schemaToString(schema, FormatFlags.UseAlias)
stringify(schema, { alias: true })
Trim code usages and TypeScript definitions
createOpenAPIBaseRenderer() from fumadocs-openapi registers no code usage generators and no TypeScript definitions, so a page built on it bundles only what you pass:
import { createCodeUsageGeneratorRegistry } from 'fumadocs-openapi/requests/generators';import { curl } from 'fumadocs-openapi/requests/generators/curl';createOpenAPIBaseRenderer({ shiki, codeUsages: createCodeUsageGeneratorRegistry().register(curl), components: { ... },});
createOpenAPIRenderer() and fumadocs-openapi/ui register every language and TypeScript definitions for you.
Remove useStorageKey()
The hook returned (name) => storageKeyPrefix + name. Read the prefix from the page instead:
It held the UI the integrations share, and that UI is now either bundled into them or installed with Fumadocs CLI, so nothing imports it by name any more. If you imported it directly:
Before
Now
@fumadocs/api-docs/schema/*
@fumadocs/json-schema
@fumadocs/api-docs/components/schema*
npx @fumadocs/cli add fumadocs/api-docs/schema
@fumadocs/api-docs/components/* (the UI)
installed with the component that uses it
@fumadocs/api-docs/i18n
the integration's own Translations covers its keys
@fumadocs/api-docs/css/preset.css
already included by the integration's preset
The CLI namespace is unchanged, fumadocs/api-docs/schema still installs the Schema UI.
Headless API pages
API pages are now built on a headless layer, use it to build your own UI:
createAsyncAPIRenderer() and <AsyncAPIProvider /> with your own components.
the hooks of pages and operations: useAsyncAPI(), useComponents(), useRenderContext(), useServer(), useOperation() and useOperationSecurity().
useServer() resolves server URLs: resolveUrl(id) fills in the variables of a server, and the selected one carries its title.
@fumadocs/asyncapi/ui renders through the layer, its options are unchanged except content.renderAPIExampleLayout, which was never rendered and is removed.
Install the UI
The UI of API pages can be installed with Fumadocs CLI and edited, reusing the components/ui files you already have:
npx @fumadocs/cli add fumadocs/asyncapi/page
It installs <AsyncAPIPage /> itself, import it from @/components/asyncapi/page in place of your components/api-page.tsx.
To replace parts of it, install fumadocs/asyncapi/operation or fumadocs/api-docs/schema and pass them to the new components options:
The option was never rendered by API pages, and it is gone with its @fumari/json-schema-ts dependency. Passing it is now a type error, nothing else changes.
Client-safe package entry
generateFiles() reads and writes files, so the package entry ships a stubbed build under the browser condition. Client components can import createAsyncAPIRenderer() and the hooks without pulling node:fs into the bundle.
Highlighting out of the box
createAsyncAPIRenderer() highlights code blocks with the full Shiki bundle, pass a smaller shiki factory to trim it.
Default page components
createOpenAPIRenderer(), createAsyncAPIRenderer() and createGraphQLRenderer() fill the Markdown, CodeBlock and Heading components you didn't pass, rendering Markdown through Remark and code blocks through Shiki:
Select and Input follow the Shadcn UI API, so a project that already has them keeps its own. @fumadocs/story no longer ships a second copy of either.
labelVariants moved to the installed label component, leaving the input a plain Shadcn-compatible primitive.
The integrations share one implementation of these internally, instead of each keeping a copy: the selected server and its variables, the state of an async request, the coloured label of methods and kinds, and the plain-object check of both schema layers.
The request pipeline of the playground stays in the package too, so an installed playground drives it instead of copying it: encodeRequestData(), resolveMediaAdapter(), isMediaTypeSupported() and the request data types come from fumadocs-openapi/requests, and createBrowserFetcher() with usePlaygroundAuth() from fumadocs-openapi/playground.
@fumadocs/json-schema
The JSON Schema utilities of API pages are now 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 renders a schema into the data an API page draws: generateSchemaUI() with the SchemaData and InfoTag types. It was in the Schema UI before, where every install copied it. A labelled tag can be prose, for values like a Markdown deprecation reason.
They were @fumadocs/api-docs/schema/* before, and the API was cleaned up while moving:
Before
Now
ParsedSchema
JsonSchema
NoReference / NoReferenceSwallow
Dereferenced / DereferencedShallow
dereferenceShallow(schema)
dereference(schema)
matchesSchema(schema, value)
matches(schema, value)
typeMatches(value, type)
matchesType(value, type)
schemaToString(schema, FormatFlags.UseAlias)
stringify(schema, { alias: true })
Trim code usages and TypeScript definitions
createOpenAPIBaseRenderer() from fumadocs-openapi registers no code usage generators and no TypeScript definitions, so a page built on it bundles only what you pass:
import { createCodeUsageGeneratorRegistry } from 'fumadocs-openapi/requests/generators';import { curl } from 'fumadocs-openapi/requests/generators/curl';createOpenAPIBaseRenderer({ shiki, codeUsages: createCodeUsageGeneratorRegistry().register(curl), components: { ... },});
createOpenAPIRenderer() and fumadocs-openapi/ui register every language and TypeScript definitions for you.
Remove useStorageKey()
The hook returned (name) => storageKeyPrefix + name. Read the prefix from the page instead:
It held the UI the integrations share, and that UI is now either bundled into them or installed with Fumadocs CLI, so nothing imports it by name any more. If you imported it directly:
Before
Now
@fumadocs/api-docs/schema/*
@fumadocs/json-schema
@fumadocs/api-docs/components/schema*
npx @fumadocs/cli add fumadocs/api-docs/schema
@fumadocs/api-docs/components/* (the UI)
installed with the component that uses it
@fumadocs/api-docs/i18n
the integration's own Translations covers its keys
@fumadocs/api-docs/css/preset.css
already included by the integration's preset
The CLI namespace is unchanged, fumadocs/api-docs/schema still installs the Schema UI.
@fumadocs/base-ui@16.15.11
fumadocs-core@16.15.11
fumadocs-ui@16.15.11
Shadcn UI compatible primitives
The primitives in fumadocs-ui/components/ui/* now follow the API of Shadcn UI, so components installed by the CLI can use the ones you already have.
buttonVariants accepts the default variant of Shadcn UI:
fumadocs-ui/components/ui/scroll-area is removed, the sidebars render the scroll area primitives directly.
Mark packages side-effect free
All packages now declare sideEffects in package.json, so bundlers can tree-shake unused modules. Packages shipping stylesheets list them as side effects to keep CSS imports.