modelcontextprotocol / modelcontextprotocol/inspector
Investigate migrating from unmaintained tsup to tsdown
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 10.9k
- Forks
- 1.5k
- Avg merge
- 6h 17m
- Merged PRs (30d)
- 151
Description
Background
The CLI and TUI clients (and test-servers) currently bundle with tsup, which is effectively unmaintained. tsdown is the actively-maintained, Rolldown-powered successor positioned as a drop-in replacement.
Goal
Investigate why we're on tsup and evaluate migrating to tsdown.
Tasks
- Inventory every place
tsupis used (clients/cli,clients/tui,test-servers, any others) and the config/options each relies on. - Assess
tsdowncompatibility with those configs (entry points, formats, dts, externals, the@inspector/corealias, watch mode). - Prototype the migration for one client and confirm builds + tests pass.
- Document findings and recommend whether/how to migrate.
Acceptance criteria
- A clear recommendation on migrating to
tsdown, with the migration path and any blockers identified.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inventorying tsup usage in clients/cli, clients/tui, test-servers, and any other locations, including each config's entry points, formats, dts, externals, @inspector/core alias, and watch mode. Prototype tsdown for one client, then run the relevant builds and tests. Document compatibility, blockers, migration steps, and a clear recommendation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, cli, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100