chore(deps): bump fumadocs-ui from 16.14.3 to 16.15.4 in /apps/docs-next

[dependabot]

Bumps fumadocs-ui from 16.14.3 to 16.15.4.

Release notes

Sourced from fumadocs-ui's releases.

fumadocs@16.15.4

• @​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.

fumadocs@16.15.3

• @​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.

Fix #3509

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.

// fumadocs-mdx collection config
postprocess: {
  includeProcessedMarkdown: { output: 'function' },
},

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.

... (truncated)

Commits

• 7d6fb97 Merge pull request #3516 from fuma-nama/tegami/version-packages
• 2d4706f chore: bump deps
• e616cb3 fix(ui): improve solar theme on new \<main> container
• 19442a3 feat(openapi): support 3.2 tag group
• a9054b3 fix(openapi): also upgrade the external documents
• dbf0f12 fix(ui): Next.js auto-scroll bug
• 5cd7b69 Merge pull request #3510 from fuma-nama/tegami/version-packages
• 814559b docs: introduce React Markdown Components
• b4d689d refactor(core(: rename options
• eefd3e0 feat(satteri): show the type table as a table in markdown form
• Additional commits viewable in compare view