docusaurus-develop

Resolve Docusaurus v3/v4 warnings and module-not-found errors with configuration fixes.

11|1|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/Takazudo/claude-resources --skill docusaurus-develop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docusaurus-develop
Source: https://github.com/Takazudo/claude-resources/tree/main/skills/docusaurus-develop
Command: npx skills add https://github.com/Takazudo/claude-resources --skill docusaurus-develop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Docusaurus sites often encounter warnings about onBrokenMarkdownLinks and module-not-found errors when swizzling components or using pnpm, which blocks development and slows iteration. This section provides a concise set of fixes and best practices to keep builds green.

Core Features & Use Cases

  • Suppress Broken Link Warnings: Configure onBrokenLinks and onBrokenMarkdownLinks under markdown.hooks to reduce noise from generated or merged documentation.
  • Explicit PNPM Dependencies for Swizzled Components: Install @docusaurus/theme-common and @docusaurus/plugin-content-docs to ensure dependencies are hoisted and resolvable under pnpm.
  • Guided Troubleshooting: Step-by-step guidance for common module-not-found issues and deprecated config warnings during site development.

Quick Start

Start the Docusaurus dev server for your site and apply the documented fixes to suppress warnings and resolve module errors.

Frequently Asked Questions about docusaurus-develop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix module-not-found errors when swizzling Docusaurus components with pnpm?

Module-not-found errors during Docusaurus component swizzling with pnpm are resolved by explicitly installing dependencies like @docusaurus/theme-common and @docusaurus/plugin-content-docs to ensure proper hoisting and resolvability.

Why does Docusaurus show onBrokenMarkdownLinks warnings and how do I suppress them?

Docusaurus shows onBrokenMarkdownLinks warnings when generated or merged documentation contains unresolved references. Suppress this noise by configuring onBrokenMarkdownLinks under the markdown.hooks section in your configuration file.

Does Docusaurus v3 and v4 support the markdown.hooks configuration for broken links?

Yes, Docusaurus v3 and v4 support the markdown.hooks configuration. Placing onBrokenLinks and onBrokenMarkdownLinks under markdown.hooks is the correct best-practice step to keep builds stable and suppress deprecated config warnings.

What's the best way to resolve deprecated configuration warnings during Docusaurus site development?

The best way to resolve deprecated Docusaurus configuration warnings is to follow guided troubleshooting steps, including moving broken link settings to markdown.hooks and managing swizzled component dependencies explicitly.

How do I keep Docusaurus builds stable when working with generated docs that have broken references?

Keep Docusaurus builds stable with generated docs by configuring onBrokenMarkdownLinks under markdown.hooks to reduce noise, and by explicitly installing required theme dependencies to prevent module resolution failures.