Saket Aryan
92aa8a1de1
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
30 lines
838 B
JSON
30 lines
838 B
JSON
{
|
|
"$schema": "https://json.schemastore.org/tsconfig",
|
|
"compilerOptions": {
|
|
"composite": false,
|
|
"declaration": true,
|
|
"declarationMap": true,
|
|
"esModuleInterop": true,
|
|
"forceConsistentCasingInFileNames": true,
|
|
"inlineSources": false,
|
|
"isolatedModules": true,
|
|
"moduleResolution": "node16",
|
|
"noUnusedLocals": false,
|
|
"noUnusedParameters": false,
|
|
"preserveWatchOutput": true,
|
|
"resolveJsonModule": true,
|
|
"skipLibCheck": true,
|
|
"strict": true,
|
|
"types": ["@types/node", "jest"],
|
|
"jsx": "react-jsx",
|
|
"lib": ["dom", "ES2021"],
|
|
"module": "Node16",
|
|
"target": "ES2018",
|
|
"stripInternal": true,
|
|
"paths": {
|
|
"@/*": ["./src/*"]
|
|
}
|
|
},
|
|
"include": ["."],
|
|
"exclude": ["dist", "build", "node_modules"]
|
|
} |