singularity/singularity-forge
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

fix(mcp): use createRequire to resolve SDK wildcard subpath imports

Browse source 
Node ESM can't resolve wildcard export patterns without .js extension.
The MCP SDK's server/stdio and types subpaths use wildcard exports that
fail at runtime with ERR_MODULE_NOT_FOUND.

Use createRequire (CJS resolver) to resolve physical file paths before
passing to dynamic import(), since CJS auto-appends .js.

Closes #3603

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Tibsfox 2026-04-06 19:17:26 -07:00
parent b4c6229360
commit 8fbb0cd1eb
1 changed files with 6 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
src/mcp-server.ts
View file

@ -19,6 +19,10 @@ export interface McpToolDef {
// MCP SDK subpath imports use wildcard exports (./*) that NodeNext resolves
// at runtime but TypeScript cannot statically type-check. We construct the
// specifiers dynamically so tsc treats them as `any`.
// Use createRequire to resolve wildcard subpaths — CJS resolver auto-appends
// .js, which the ESM wildcard export map does not (#3603).
import { createRequire } from 'node:module'
const _require = createRequire(import.meta.url)
const MCP_PKG = '@modelcontextprotocol/sdk'
/**
@ -42,8 +46,8 @@ export async function startMcpServer(options: {
const { tools, version = '0.0.0' } = options
const serverMod = await import(`${MCP_PKG}/server`)
const stdioMod = await import(`${MCP_PKG}/server/stdio`)
const typesMod = await import(`${MCP_PKG}/types`)
const stdioMod = await import(_require.resolve(`${MCP_PKG}/server/stdio`))
const typesMod = await import(_require.resolve(`${MCP_PKG}/types`))
const Server = serverMod.Server
const StdioServerTransport = stdioMod.StdioServerTransport