[chore] Update MCP DevKit server to use ESM/vitest #16
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zmofei
approved these changes
Sep 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR addresses a number of issues for the MCP Server:
Moves to proper ESM/CJS dual emitting via tshy
Eliminates the patching of fetch and instead creates a pipeline which adds a retry policy and user agent policy
Migrates tests from jest to vitest for better ESM support
Fixes code emitting to NodeNext instead of ESNext and fixes import inconsistencies
Closes
This closes the following work items:
Testing
Adds additional unit tests for the following:
Checklist
Additional Notes