fix(packages): add types/typesVersions for legacy moduleResolution: node

[felixweinberger]

Part of the v2 backwards-compatibility series — see reviewer guide.

v2 packages use exports maps only. TypeScript's legacy moduleResolution: node (Node10) ignores exports, so every import is TS2307. This adds types to leaf packages and a narrow typesVersions map where subpaths exist.

Motivation and Context

v2 packages use exports maps only. TypeScript's legacy moduleResolution: node (Node10) ignores exports, so every import is TS2307. This adds types to leaf packages and a narrow typesVersions map where subpaths exist.

v1 vs v2 pattern & evidence

v1 pattern:

v1 also relied on `exports`, but legacy resolution worked for the root because v1 had `main`/`types` fields

v2-native:

Same — but the naive `typesVersions: {*:{*:[dist/*]}}` form *breaks* (remaps `types` through itself). This is the correct narrow form.

Evidence: Validated against tsconfigs using moduleResolution: node — resolves cleanly.

How Has This Been Tested?

• Typecheck IS the test
• Integration: validated bump-only against 5 OSS repos via the v2-bc-integration validation branch
• pnpm typecheck:all && pnpm lint:all && pnpm test:all green

Breaking Changes

None — additive @deprecated shim. Removed in v3.

Types of changes

• New feature (non-breaking change which adds functionality)

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added or updated documentation as needed

Additional context

Stacks on: none

[changeset-bot]

🦋 Changeset detected

Latest commit: 8d41f04

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 6 packages

Name	Type
@modelcontextprotocol/client	Patch
@modelcontextprotocol/server	Patch
@modelcontextprotocol/node	Patch
@modelcontextprotocol/express	Patch
@modelcontextprotocol/fastify	Patch
@modelcontextprotocol/hono	Patch

Not sure what this means? Click here to learn what changesets are.

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

[pkg-pr-new]

Open in StackBlitz

@modelcontextprotocol/client

npm i https://pkg.pr.new/@modelcontextprotocol/client@1898

@modelcontextprotocol/server

npm i https://pkg.pr.new/@modelcontextprotocol/server@1898

@modelcontextprotocol/express

npm i https://pkg.pr.new/@modelcontextprotocol/express@1898

@modelcontextprotocol/fastify

npm i https://pkg.pr.new/@modelcontextprotocol/fastify@1898

@modelcontextprotocol/hono

npm i https://pkg.pr.new/@modelcontextprotocol/hono@1898

@modelcontextprotocol/node

npm i https://pkg.pr.new/@modelcontextprotocol/node@1898

commit: 8d41f04