Skip to content

fix: declare zod as a runtime dependency - #38

Open
mharnett wants to merge 1 commit into
CognitionAI:mainfrom
mharnett:fix/declare-zod-dependency
Open

fix: declare zod as a runtime dependency#38
mharnett wants to merge 1 commit into
CognitionAI:mainfrom
mharnett:fix/declare-zod-dependency

Conversation

@mharnett

@mharnett mharnett commented Jul 5, 2026

Copy link
Copy Markdown

Problem

zod is imported in five source files but is not declared in package.json:

src/tools/card-tools.ts:1:      import { z } from "zod";
src/tools/additional-tools.ts:1:import { z } from "zod";
src/tools/dashboard-tools.ts:1: import { z } from "zod";
src/tools/table-tools.ts:1:     import { z } from "zod";
src/tools/database-tools.ts:1:  import { z } from "zod";

It's absent from dependencies, devDependencies, and peerDependencies, so it currently only resolves transitively (e.g. via fastmcp). If that transitive path ever drops or moves zod, a fresh npm install of @cognitionai/metabase-mcp-server would fail to resolve it at runtime.

Fix

Declare zod explicitly in dependencies (^3.25.76, matching the major already used transitively). One line; no code changes.


Devin Review

Status Commit
⚪ Not started

Run Devin Review

💡 Connect your GitHub account to enable automatic code reviews.

Open in Devin Review (Staging)

zod is imported in src (src/tools/{card,additional,dashboard,table,database}-tools.ts
all `import { z } from "zod"`) but is not listed in any dependency bucket of
package.json. It currently resolves only transitively (e.g. via fastmcp), so a
fresh end-user install could fail to resolve zod if that transitive path
changes. Declare it explicitly in dependencies.
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