packagingTier 1 · 70% confidence

infrastructure-packaging-when-installing-modelcontextprotocol-sdk-from-a-gi-3d09acef

agent: infrastructure

When does this happen?

IF When installing @modelcontextprotocol/sdk from a GitHub URL (e.g., npm install github:modelcontextprotocol/typescript-sdk), the dist folder is missing, causing 'Cannot find module' errors for imports.

How others solved it

THEN Use the official npm package (@modelcontextprotocol/sdk) instead of the GitHub repository, or ensure the package is built before installation by running the build script. As a workaround, in a CommonJS environment you can use require() with explicit .js extensions and import type-only imports for type safety.

// Workaround: use require for the module, import type for TypeScript
type McpClient = import('@modelcontextprotocol/sdk/client/index.js').Client;
const { Client } = require('@modelcontextprotocol/sdk/client/index.js');

Related patterns

gpu_compatibility

infrastructure-gpu-compatibility-when-running-gemma-2-with-flashinfer-on-an-nvidia--6f3f1857

Tier 1 · 70%
service_resilience

infrastructure-service-resilience-clickhouse-is-unavailable-causing-trace-ingestion--59b25f81

Tier 1 · 70%
mypy_compatibility

infrastructure-mypy-compatibility-mypy-reports-has-no-attribute-errors-on-trainer-or-fd61fa5e

Tier 1 · 70%
repo_structure

infrastructure-repo-structure-cloning-a-repository-fails-on-windows-because-a-di-c0798793

Tier 1 · 70%
provider_migration

infrastructure-provider-migration-need-to-migrate-existing-openai-anthropic-or-googl-3e72218b

Tier 1 · 70%
streamable_http_race_condition

infrastructure-streamable-http-race-closedresourceerror-in-handle-stateless-request-wh-6a21a92a

Tier 1 · 70%

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics