fix: keep optional MCP imports out of bundles - #285
Merged
Conversation
|
@onmax is attempting to deploy a commit to the NuxtLabs Team on Vercel. A member of the Team first needs to authorize it. |
antfu
approved these changes
Aug 24, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
What
Resolve the optional MCP adapter at runtime from the installed
devframepackage.devframe/initiate,devframe/adapters/cac,@devframes/hub/initiate, and@devframes/next/hubno longer expose the adapter or its optional SDK peer to consumer bundle graphs.Enabling MCP still loads the same adapter. Bundle-level coverage exercises a complete MCP initialize handshake.
Why
A literal dynamic import remains visible to bundlers. As a result, bundling an ordinary
@devframes/hub/initiateconsumer failed unless@modelcontextprotocol/serverwas installed, even when MCP was disabled.