chore(deps): bump the fumadocs group across 1 directory with 3 updates - #482

Sourced from fumadocs-core's releases.

[email protected]

• @​fumadocs/base-ui@​16.15.9
• [email protected]
• [email protected]

getPageByUrl() on the loader

Look up a page by its URL:

source.getPageByUrl('/docs/getting-started');
source.getPageByUrl('/cn/docs/getting-started', 'cn');

Without the language argument every language is looked up, unlike getPageByHref() which resolves the default language only.

llms() renders pages

llms() used to build the llms.txt index only, turning a page into Markdown was left to your own getLLMText(). Pass renderPage and it covers both:

import { llms } from 'fumadocs-core/source';
export const docsLlms = llms(source, {
renderPage: async (page) => `# ${page.data.title} (${page.url})
${await page.data.getText('processed')}`,
});

• page(page) renders one page, for the per-page Markdown route.
• full(lang?) renders every page and joins them, for llms-full.txt.

// app/llms-full.txt/route.ts
export const GET = async () => new Response(await docsLlms.full());

Both methods exist only when renderPage is given, in types and at runtime. Fumadocs cannot know how your content source exposes Markdown: page.data.getText('processed') on Fumadocs MDX, page.data.content on @fumadocs/local-md.

fumadocs-core/mcp: docs tools for your MCP server

Register the docs tools on a server you own, rather than on a handler Fumadocs builds for you:

import { createMcpHandler, McpServer } from '@modelcontextprotocol/server';
import { registerSearchTool, registerSourceTools } from 'fumadocs-core/mcp';
import { createFromSource } from 'fumadocs-core/search/server';
import { docsLlms, source } from '@/lib/source';
</tr></table>

... (truncated)

• 24e2072 Version Packages (#3542)
• 191baf0 fix build
• 1c1f0d9 refactor(cli): dedupe helpers
• a74d2e8 feat(openapi): expose path on custom hooks
• 0caafd1 refactor(cli): use cac
• c5ed5eb refactor(*): clean URL helpers
• 824a028 feat(core,cli): handle dynamic source
• ff009e3 feat(core,epub): move some utils to core
• 27af24c docs: add OpenPost to showcase (#3544)
• 07c46a2 docs: generate webmcp
• Additional commits viewable in compare view

Sourced from fumadocs-mdx's releases.

[email protected]

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.

[email protected]

Scope lastModified git log to the content directory

git log is scoped to the collection's content directory instead of buffering the repository's entire history in every worker.

Fix Vite dev server crash on declaration-only dependencies

The injected Vite config no longer pre-bundles packages without runtime JavaScript, such as @types/mdx. Pre-bundling them made esbuild parse .d.ts files and fail on imports that only exist in type space, crashing the dev server.

Encode import.meta.glob query values

The Vite codegen passed the query to import.meta.glob as an object, letting the bundler serialize it. Rolldown inlines the values as-is, so a macro id such as src/lib/source.ts#docs left an unescaped / in the content file's module id and relative imports from that module (e.g. images from ![Banner](https://github.com/fuma-nama/fumadocs/blob/HEAD/logo.png)) failed to resolve, since the importer's directory is derived from the raw id.

The query is now serialized (and percent-encoded) by Fumadocs itself, matching what the Node.js codegen already did.

[email protected]

Sätteri 0.10

@fumadocs/satteri now requires satteri ^0.10.3, and the plugins were rewritten on its new capabilities:

• Exports (frontmatter, toc, structuredData, …) are emitted by an after document hook instead of an anchor marker appended to the source, so plugins no longer see (or need to skip) the anchor node.

... (truncated)

• 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
• 49afb7d docs: support .md apart from .mdx suffix
• 399bea9 feat(mdx,satteri): support dynamic markdown renderer on remark-llms plugin
• 7eef0d8 feat(core): React Markdown Component
• 3d07ef5 fix(core): duplicated record when indexing
• 0687a8b Version Packages (#3507)
• cc53d34 internal(core): drop negotiator
• Additional commits viewable in compare view

Sourced from fumadocs-ui's releases.

[email protected]

• @​fumadocs/base-ui@​16.15.9
• [email protected]
• [email protected]

getPageByUrl() on the loader

Look up a page by its URL:

source.getPageByUrl('/docs/getting-started');
source.getPageByUrl('/cn/docs/getting-started', 'cn');

Without the language argument every language is looked up, unlike getPageByHref() which resolves the default language only.

llms() renders pages

llms() used to build the llms.txt index only, turning a page into Markdown was left to your own getLLMText(). Pass renderPage and it covers both:

import { llms } from 'fumadocs-core/source';
export const docsLlms = llms(source, {
renderPage: async (page) => `# ${page.data.title} (${page.url})
${await page.data.getText('processed')}`,
});

• page(page) renders one page, for the per-page Markdown route.
• full(lang?) renders every page and joins them, for llms-full.txt.

// app/llms-full.txt/route.ts
export const GET = async () => new Response(await docsLlms.full());

Both methods exist only when renderPage is given, in types and at runtime. Fumadocs cannot know how your content source exposes Markdown: page.data.getText('processed') on Fumadocs MDX, page.data.content on @fumadocs/local-md.

fumadocs-core/mcp: docs tools for your MCP server

Register the docs tools on a server you own, rather than on a handler Fumadocs builds for you:

import { createMcpHandler, McpServer } from '@modelcontextprotocol/server';
import { registerSearchTool, registerSourceTools } from 'fumadocs-core/mcp';
import { createFromSource } from 'fumadocs-core/search/server';
import { docsLlms, source } from '@/lib/source';
</tr></table>

... (truncated)

• 24e2072 Version Packages (#3542)
• 191baf0 fix build
• 1c1f0d9 refactor(cli): dedupe helpers
• a74d2e8 feat(openapi): expose path on custom hooks
• 0caafd1 refactor(cli): use cac
• c5ed5eb refactor(*): clean URL helpers
• 824a028 feat(core,cli): handle dynamic source
• ff009e3 feat(core,epub): move some utils to core
• 27af24c docs: add OpenPost to showcase (#3544)
• 07c46a2 docs: generate webmcp
• Additional commits viewable in compare view