Skip to content

fix: resolve TypeDoc warnings from directory-pointing relative links#1546

Merged
jonathanhefner merged 2 commits intomodelcontextprotocol:mainfrom
jonathanhefner:fix-typedoc-warnings
Feb 17, 2026
Merged

fix: resolve TypeDoc warnings from directory-pointing relative links#1546
jonathanhefner merged 2 commits intomodelcontextprotocol:mainfrom
jonathanhefner:fix-typedoc-warnings

Conversation

@jonathanhefner
Copy link
Member

Replace relative markdown links that point to directories with absolute GitHub URLs. TypeDoc cannot copy directories to the output, so these produced warnings that failed the build under treatWarningsAsErrors.

  • README.md: examples/ and packages/middleware/ links
  • packages/middleware/{express,hono,node}/README.md: ../../server/ links

Also drop --emit none from docs:check. TypeDoc only validates relative-link targets during the render phase (in
AssetsPlugin.onRenderEnd), so --emit none silently skips these checks and docs:check passes even when docs would fail. Until this is fixed upstream, a full build is needed for docs:check to be a reliable CI gate.

Replace relative markdown links that point to directories with absolute
GitHub URLs. TypeDoc cannot copy directories to the output, so these
produced warnings that failed the build under `treatWarningsAsErrors`.

- README.md: `examples/` and `packages/middleware/` links
- packages/middleware/{express,hono,node}/README.md: `../../server/`
  links

Also drop `--emit none` from `docs:check`. TypeDoc only validates
relative-link targets during the render phase (in
AssetsPlugin.onRenderEnd), so `--emit none` silently skips these checks
and `docs:check` passes even when `docs` would fail. Until this is fixed
upstream, a full build is needed for `docs:check` to be a reliable CI
gate.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@jonathanhefner jonathanhefner requested a review from a team as a code owner February 16, 2026 18:30
@changeset-bot
Copy link

changeset-bot bot commented Feb 16, 2026

⚠️ No Changeset found

Latest commit: 437f11a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@pkg-pr-new
Copy link

pkg-pr-new bot commented Feb 16, 2026

Open in StackBlitz

@modelcontextprotocol/client

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/client@1546

@modelcontextprotocol/server

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/server@1546

@modelcontextprotocol/express

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/express@1546

@modelcontextprotocol/hono

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/hono@1546

@modelcontextprotocol/node

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/node@1546

commit: 437f11a

@jonathanhefner jonathanhefner merged commit 2b620d7 into modelcontextprotocol:main Feb 17, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants