chore(deps): bump fumadocs-mdx from 14.3.0 to 15.3.0

[dependabot]

Bumps fumadocs-mdx from 14.3.0 to 15.3.0.

Release notes

Sourced from fumadocs-mdx's releases.

fumadocs-mdx@15.3.0

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.
• remark-steps, remark-admonition and remark-code-tab still detect their targets through node visitors (so documents without the construct cost nothing), but process each parent exactly once in an after hook, replacing the per-visit dedup workarounds.
• remark-llms stringifies the document root from a before hook instead of subscribing to 19 node types to find it.
• Markdown documents compile through Sätteri's own markdownToJs; the hand-assembled pipeline is gone. Raw HTML in .md files is still dropped, matching the previous behavior.
• rehype-katex parses KaTeX output with Sätteri's htmlToHast, dropping the hast-util-from-html dependency.
• No plugin reads node.position, so Sätteri now skips source-position tracking entirely (~15% faster parse).

Breaking: ExtraPluginHooks.beforeToJs was removed. Seed ctx.data from a Sätteri before hook on the plugin definition instead — it also receives the document root:

import { defineMdastPlugin } from 'satteri';
defineMdastPlugin({
name: 'my-plugin',
before(root, ctx) {
ctx.data.myValue ??= [];
},
});

fumadocs-mdx@15.2.3

Fix Base UI's use-sync-external-store breaking Vite dev servers

The Vite config is now derived from your project's own dependencies at startup, instead of being generated ahead of time against ours.

Builds keep the alias that replaces the shim with React, which is now applied only there. Pre-bundling is a dev server feature, and on builds a bundler that leaves the shim's require('react') in place gives it a second React instance whose hook dispatcher is null, breaking every component with a Base UI store.

fumadocs-mdx@15.2.2

Support thenable Next.js config

Allow the promises to be awaited.

fumadocs-mdx@15.2.1

Support simpler fumadocsMdx vite plugin usage

Use the fumadocsMdx method instead for better syntax around macro usage.

Support browser helpers for Macro API

Use preload & lazy body renderer on non-rsc environment.

fumadocs-mdx@15.2.0

Support Macro API

Use fumadocs-mdx/macro to define collections, and enable the macro-style API from bundler plugin (e.g. createMDX) using the include option.

... (truncated)

Commits

• 3cfb127 Merge pull request #3488 from fuma-nama/tegami/version-packages
• e46a700 feat(mdx,satteri): use satteri 0.10
• 3043da2 Version Packages (#3486)
• 671bd83 feat(core): support baseSlugs option
• 2899bc1 fix(ui): add a main landmark to docs, notebook and flux pages (#3483)
• 14f9eaf feat(core): support next param for custom slugs function
• ddccb91 docs: improve local-html section
• 43f4006 Version Packages (#3478)
• d1c99ad chore(local-html): improve DX
• 7fd880d example: add for html content source
• Additional commits viewable in compare view

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
databuddy-status	Error		Aug 26, 2026 10:10am
documentation	Error		Aug 26, 2026 10:10am

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
dashboard	Skipped		Aug 26, 2026 10:10am

[unkey-deploy]

The latest updates on your projects. Learn more about Unkey Deploy

Name	Status	Preview	Inspect	Updated (UTC)
links (preview)	Ready	Visit Preview	Inspect	Aug 26, 2026 10:09am

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.