whatisgithub

What is rsdoctor?

web-infra-dev/rsdoctor — explained in plain English

Analysis updated 2026-05-18

1,132TypeScriptAudience · developerComplexity · 3/5LicenseSetup · moderate

In one sentence

A build analyzer that shows developers why their Rspack or webpack builds are slow or producing unexpectedly large bundles.

Mindmap

mindmap
  root((Rsdoctor))
    What it does
      Build analysis
      Bundle inspection
      Rule checks
    Tech stack
      TypeScript
      Rspack
      webpack
    Use cases
      Slow build diagnosis
      Duplicate package detection
    Audience
      Frontend developers
      Build tool maintainers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Diagnose why a build is slow by seeing timing for each build step

USE CASE 2

Find duplicate packages or version inconsistencies in a bundle

USE CASE 3

Visualize module dependencies to understand a large bundle

USE CASE 4

Write custom rules to catch project-specific build problems

What is it built with?

TypeScriptRspackwebpack

How does it compare?

web-infra-dev/rsdoctorant-design/ant-design-web3xrpcommunity/xrp-community-wallet
Stars1,1321,1321,140
LanguageTypeScriptTypeScriptTypeScript
Last pushed2026-06-15
MaintenanceMaintained
Setup difficultymoderateeasymoderate
Complexity3/52/52/5
Audiencedeveloperdevelopergeneral

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Requires plugging into an existing Rspack or webpack build setup.

Use freely for any purpose, including commercial use, under the MIT license.

So what is it?

Rsdoctor is a build analyzer tool for developers who use Rspack or webpack, two popular bundlers (programs that take your project's many files and combine them into one or a few optimized files for the browser). When your project's build process is slow or producing unexpected results, Rsdoctor helps you figure out exactly why. The tool works by plugging into your existing build setup and collecting detailed data about what happened during the build: how long each step took, which code modules depend on which other modules, and whether any problematic patterns exist in your code. It then presents this information through visual charts and reports, making it easy to spot slowdowns, duplicate packages, or version inconsistencies without having to read raw log files. You would reach for Rsdoctor when your app's build is taking too long and you're not sure where the bottleneck is, or when your final bundle (the output file) is larger than expected and you want to understand why. It also includes automated rules that check for common problems and can flag them automatically, and you can write your own custom rules if you have project-specific concerns. Rsdoctor is written in TypeScript and works with a wide range of frameworks and tools that are built on top of Rspack or webpack. It is part of the Rstack family of JavaScript tooling. The project is open source under the MIT license.

Copy-paste prompts

Prompt 1
How do I add Rsdoctor to my existing Rspack or webpack config?
Prompt 2
How can I use Rsdoctor to find out why my bundle size increased?
Prompt 3
How do I write a custom Rsdoctor rule to flag duplicate dependencies?

Frequently asked questions

What is rsdoctor?

A build analyzer that shows developers why their Rspack or webpack builds are slow or producing unexpectedly large bundles.

What language is rsdoctor written in?

Mainly TypeScript. The stack also includes TypeScript, Rspack, webpack.

What license does rsdoctor use?

Use freely for any purpose, including commercial use, under the MIT license.

How hard is rsdoctor to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is rsdoctor for?

Mainly developer.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.