chore: update Dockerfile and CI configuration for Node 20, enhance pa…

[agoldis]

…ckage structure

• Updated Dockerfile to use Node 20 for both build and runtime stages.
• Modified GitHub Actions workflow to support testing across Node versions 20.x, 22.x, and 24.x.
• Enhanced package.json to include new module exports and updated dependencies.
• Introduced tsconfig.cjs.json for CommonJS builds and adjusted TypeScript configurations.
• Added new scripts for CJS package JSON generation and updated test scripts for improved coverage.
• Refactored source code structure, including the introduction of an API entry point and integration tests for ESM and CJS compatibility.

---

Summary by cubic

Move to a dual ESM/CJS build with a clean programmatic API, keep the CLI stdio entrypoint, and adopt Node 20 across Docker and CI. Adds clear failure handling when CURRENTS_API_KEY is missing.

• New Features

  • Ship dual ESM/CJS builds with an exports map and a new startMcpServer entry point; CLI stdio stays in src/index.ts, server/tool registration moves to src/server.ts; src/api.ts exposes programmatic exports; tools now use direct zod schemas.
  • Integration tests for ESM import, CJS require and dynamic import, CLI bin/npx via npm pack, and published tarball resolution via import "@currents/mcp"; tests build first, increase CLI test timeout, and mock CURRENTS_API_KEY for startup.
  • Error handling: throw on missing CURRENTS_API_KEY (MISSING_CURRENTS_API_KEY_MESSAGE); CLI logs a short guidance message without a stack trace.
  • Platform/deps: Docker and CI on Node 20; CI matrix 20.x/22.x/24.x; upgrade @modelcontextprotocol/sdk to ^1.28.0.

• Migration

  • Requires Node >=20 (engines updated).
  • Programmatic usage:
    • ESM: import { startMcpServer } from @currents/mcp
    • CJS: const { startMcpServer } = require(@currents/mcp) or import(@currents/mcp)

^{Written for commit da86eed. Summary will update on new commits.}

[cubic-dev-ai]

1 issue found across 14 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="mcp-server/src/server.ts">

<violation number="1" location="mcp-server/src/server.ts:44">
P2: Fail fast when the API key is missing; logging and continuing starts a server that can’t successfully call the Currents API.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}