Rsdoctor 2.0 Roadmap

[yifancong]

Goal

The core goal of Rsdoctor 2.0 is to consolidate the technology stack, focus on Rspack analysis, reduce dependency costs, optimize the package structure, and enhance analysis and execution capabilities in AI scenarios.

1. Remove Webpack Support

#1685

Goal: Focus on the Rspack ecosystem and reduce compatibility costs.

Main Work:

• Remove Webpack-related plugin logic, types, tests, and documentation.
• Reduce the maintenance cost caused by supporting two bundlers.
• Make Rsdoctor 2.0 focus on Rspack scenarios by default.

2. Dependency Optimization

Goal: Reduce installation size and dependency complexity, and minimize extra dependencies introduced when users install Rsdoctor.

Key Optimization Targets:

• es-toolkit
• arcon
• @babel/code-frame
• @rsbuild/plugin-check-syntax
• Other non-core dependencies

Main Work:

• Analyze whether these dependencies must be installed directly.
• Prefer on-demand dependencies, internal replacements, or lighter alternatives.
• Avoid polluting the main installation path with non-core features.
• Reduce lockfile complexity and installation time.

3. Package Restructuring

Goal: Merge Rsdoctor packages into a cleaner structure and reduce package count and internal dependency complexity.

Main Work:

• Consolidate foundational capability packages.
• Merge tightly coupled packages.
• Preserve core entry packages that users install directly.
• Clarify boundaries between core runtime, frontend report, CLI, plugins, and AI tools.
• Provide wrapper packages for old entries to ensure smooth migration.
• ESM only

Expected Benefits:

• Clearer package structure.
• Lower release and maintenance cost.
• Easier dependency analysis.
• Controllable migration risk for external users.

4. AI Capabilities

Goal: Evolve Rsdoctor 2.0 from a traditional performance analysis tool into an engineering analysis system that can be consumed and executed by AI.

4.1 Rsdoctor Agent CLI

Status: Completed.

Usage:

• Serve as the base entry for AI Agents to access Rsdoctor data.
• Support local diagnostics, data reading, and analysis task execution.

Main Capabilities:

• Read Rsdoctor analysis data.
• Support Agent-side querying, summarization, and diagnostics.
• Provide a foundation for future MCP, skills, actions, and other AI capabilities.

4.2 Performance Skills Support

Goal: Provide Rsdoctor performance-related skills so AI can perform performance diagnostics based on Rsdoctor data.

Main Work:

• Define performance analysis skills.
• Support diagnostics across bundle, module, chunk, loader, and plugin dimensions.
• Output actionable optimization suggestions.
• Integrate with Rsdoctor agent-cli.

4.3 Integration Between Rsdoctor Actions and AI

Status: Completed.

Goal: Integrate Rsdoctor actions into AI workflows, allowing AI not only to read reports but also to trigger analysis actions.

Main Capabilities:

• Execute specific diagnostic tasks through actions.
• Output diagnostic results in a structured format for AI.
• Support future automated analysis, issue localization, and fix suggestions.

[yifancong]

3. Package Restructuring

Background

Rsdoctor currently maintains many internal packages, including types, utils, graph, sdk, client, components, cli, rspack-plugin, and others.

This package split makes the internal dependency graph complex, increases release and maintenance cost, and makes Rsdoctor 2.0 cleanup harder, especially around package boundaries, dependency optimization, and Webpack-related cleanup.

Goal

For Rsdoctor 2.0, we plan to converge the package structure and keep only a small set of long-term packages:

packages/

• core/ -> @rsdoctor/core
• client/ -> @rsdoctor/client
• shared -> @rsdoctor/shared
• cli/ -> @rsdoctor/cli
• agent-cli/ -> @rsdoctor/agent-cli

documents/ -> docs site and docs assets

TODO

Phase 1: Core as the Node-side main package

• Move @rsdoctor/types into @rsdoctor/core/types
• Move @rsdoctor/utils into @rsdoctor/core subpaths
• Move @rsdoctor/graph into @rsdoctor/core
• Move @rsdoctor/sdk into @rsdoctor/core/sdk
• Add and verify @rsdoctor/core/* subpath exports
• Ensure @rsdoctor/core default entry does not import browser-only code
• Update internal imports and tests

Phase 2: Rspack plugin into core

• Move @rsdoctor/rspack-plugin into @rsdoctor/core
• Export RsdoctorRspackPlugin from @rsdoctor/core
• Keep @rspack/core as an optional peer dependency
• Remove standalone @rsdoctor/rspack-plugin in 2.0
• Document migration from @rsdoctor/rspack-plugin to @rsdoctor/core

Phase 3: Client and components convergence

• Merge @rsdoctor/components into @rsdoctor/client
• Move shared report UI code into client
• Ensure browser-side code does not depend on Node-only core internals
• Remove standalone @rsdoctor/components in 2.0
• Update internal and external usage examples

Phase 4: CLI remains independent

• Keep @rsdoctor/cli as the rsdoctor command entry
• Make CLI consume SDK/server/analysis capabilities from @rsdoctor/core
• Ensure CLI does not directly depend on @rspack/core
• Verify CLI install and runtime behavior

Phase 5: Agent and docs cleanup

• Keep @rsdoctor/agent-cli as the AI Agent entry
• Decide whether @rsdoctor/mcp-server should be removed or merged into agent-cli
• Update docs build, deploy, and CI paths

Phase 6: Breaking-change cleanup

• Migrate docs.
• Update migration guide
• Update examples
• Update CI/build/test configs
• Verify full build, unit tests, examples, CLI, report client, and plugin flows

Phase 7: Refactor multi plugin

• Automatically detect multi compiler scenarios and configure multi compiler