Skip to content

fix: point MCP development exports to published files#590

Open
Pugsin wants to merge 1 commit into
bssm-oss:mainfrom
Pugsin:codex/fix-mcp-development-exports
Open

fix: point MCP development exports to published files#590
Pugsin wants to merge 1 commit into
bssm-oss:mainfrom
Pugsin:codex/fix-mcp-development-exports

Conversation

@Pugsin

@Pugsin Pugsin commented Jun 17, 2026

Copy link
Copy Markdown

Summary

  • point the @codeagora/mcp development export conditions at the same published JS files as import
  • avoid resolving package exports to unpublished TypeScript source files

Why

@codeagora/mcp@0.1.2 publishes dist/index.js and dist/version.js, but not src/index.ts or src/version.ts. Consumers/tools running with the development condition can resolve those missing source files from the published package.

Validation

  • npm pack @codeagora/mcp@0.1.2 --silent confirmed package/src/index.ts and package/src/version.ts are absent while package/dist/index.js and package/dist/version.js exist
  • node -e "const p=require('./packages/mcp/package.json'); if(p.exports['.'].development!=='./dist/index.js') process.exit(1); if(p.exports['./version.js'].development!=='./dist/version.js') process.exit(2)"
  • git diff --check

Signed-off-by: Pugsin <sergio.icdlf@gmail.com>
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.

1 participant