From 92aa8a1de17385e85e3dfe8af2fc0d31b55ce4c3 Mon Sep 17 00:00:00 2001
From: Saket Aryan <saketaryan2002@gmail.com>
Date: Wed, 16 Sep 2026 22:16:20 +0530
Subject: [PATCH] fix(vercel-ai-sdk): inject the provider version at build
 instead of hardcoding it

Review finding from @karthik-indla on this PR. src/mem0-utils.ts carried
PROVIDER_VERSION = "3.0.2" as a literal. It matches package.json today and
misreports the client version from the next release bump onwards, which is the
one thing X-Mem0-Client exists to carry. Every other client in the repo injects
at build: mem0-ts via __MEM0_SDK_VERSION__, the Python side via
importlib.metadata, the CLIs via __CLI_VERSION__.

tsup now defines __MEM0_PROVIDER_VERSION__ from package.json, and the source
falls back to "dev" only when run unbundled, such as in tests. Verified in the
built bundle: PROVIDER_VERSION resolves to "3.0.2" and no placeholder survives.

resolveJsonModule is enabled alongside it, matching mem0-ts, because tsc
--noEmit covers tsup.config.ts and the package.json import fails without it.

Type check clean, build clean. The jest suite's failure is pre-existing and
unrelated: it requires a live MEM0_API_KEY, confirmed by running it on a stashed
tree. Python side 311 passed, 8 skipped; pi-agent 94 passed.

Claude-Session: https://claude.ai/code/session_01C7tEmH86HAr7GoAAKCEHZb
---
 integrations/vercel-ai-sdk/src/mem0-utils.ts | 7 ++++++-
 integrations/vercel-ai-sdk/tsconfig.json     | 1 +
 integrations/vercel-ai-sdk/tsup.config.ts    | 7 +++++++
 3 files changed, 14 insertions(+), 1 deletion(-)

diff --git a/integrations/vercel-ai-sdk/src/mem0-utils.ts b/integrations/vercel-ai-sdk/src/mem0-utils.ts
index 8fa20440c..b7a041939 100644
--- a/integrations/vercel-ai-sdk/src/mem0-utils.ts
+++ b/integrations/vercel-ai-sdk/src/mem0-utils.ts
@@ -1,4 +1,9 @@
-const PROVIDER_VERSION = "3.0.2";
+declare const __MEM0_PROVIDER_VERSION__: string | undefined;
+
+// Replaced at build time by tsup `define`. The fallback only applies when the
+// source is run unbundled, such as in tests.
+const PROVIDER_VERSION =
+  typeof __MEM0_PROVIDER_VERSION__ !== "undefined" ? __MEM0_PROVIDER_VERSION__ : "dev";
 
 import { LanguageModelV3Prompt } from '@ai-sdk/provider';
 import { Mem0ConfigSettings } from './mem0-types';
diff --git a/integrations/vercel-ai-sdk/tsconfig.json b/integrations/vercel-ai-sdk/tsconfig.json
index b05d5db02..e40350730 100644
--- a/integrations/vercel-ai-sdk/tsconfig.json
+++ b/integrations/vercel-ai-sdk/tsconfig.json
@@ -12,6 +12,7 @@
       "noUnusedLocals": false,
       "noUnusedParameters": false,
       "preserveWatchOutput": true,
+      "resolveJsonModule": true,
       "skipLibCheck": true,
       "strict": true,
       "types": ["@types/node", "jest"],
diff --git a/integrations/vercel-ai-sdk/tsup.config.ts b/integrations/vercel-ai-sdk/tsup.config.ts
index 2c8f74a6d..ff2d298c0 100644
--- a/integrations/vercel-ai-sdk/tsup.config.ts
+++ b/integrations/vercel-ai-sdk/tsup.config.ts
@@ -1,4 +1,5 @@
 import { defineConfig } from 'tsup'
+import pkg from './package.json'
 
 export default defineConfig([
   {
@@ -6,5 +7,11 @@ export default defineConfig([
     entry: ['src/index.ts'],
     format: ['cjs', 'esm'],
     sourcemap: true,
+    // Injected rather than written in the source. A hardcoded literal matches
+    // package.json on the day it is written and misreports the client version
+    // from the next release bump onwards. Same mechanism as mem0-ts.
+    define: {
+      __MEM0_PROVIDER_VERSION__: JSON.stringify(pkg.version),
+    },
   },
 ])
\ No newline at end of file