Skip to content

Conversation

@saharis9988
Copy link
Contributor

@saharis9988 saharis9988 commented Dec 6, 2025

… modules after tests migration

This PR updates the exports fields in the root package.json to match the new build output structure after the tests migration (#1220).

Motivation and Context

Since the build artifacts are now generated under dist/{cjs,esm}/src instead of directly under dist/{cjs,esm}, the exports paths must be adjusted accordingly. Without this change, all public consumer import paths resolve incorrectly.

How Has This Been Tested?

Breaking Changes

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

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

Additional context

@saharis9988 saharis9988 requested a review from a team as a code owner December 6, 2025 19:33
@pkg-pr-new
Copy link

pkg-pr-new bot commented Dec 6, 2025

Open in StackBlitz

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

commit: 84928e6

@KKonstantinov
Copy link
Contributor

Hi @saharis9988 , thanks for identifying this. Please check #1240 - it should resolve this without changing the paths.

@saharis9988
Copy link
Contributor Author

Yes, I really didn’t understand why the tests were added to the tsconfig.json.
I assumed there was a good reason for it if you did so. :)
But if we want to keep the current structure, then this is the way..

@KKonstantinov
Copy link
Contributor

KKonstantinov commented Dec 7, 2025

It's rather accidental 😅 But thanks for catching that.

Merging the other PR so we don't accidentally publish. However, we will still have to do something so /test does not light up on the describes etc. not recognizing vitest being there.

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