Files
apex-mcp-server/packages/builder/package.json
FilipBl4gojevic 949a56312a chore: raise the node floor to 22, make the libsodium step cross-platform and fail-loud, address dependency advisories
Regenerating the lockfile picked up a newer @cardano-sdk/crypto release that
dropped its errant npm-CLI runtime dependency, clearing the critical tar
advisory and 42 other advisories that traced back to it (44 -> 1, the
remainder a dev-only esbuild low). A defensive overrides pin on tar and
brace-expansion is retained per plan but is empirically not what resolved
this - documented honestly in README.md and the task report.

engines.node raised to >=22 everywhere (root + all three packages), matching
the CI workflow's node-version and the Dockerfile's node:22-alpine base
(both already agreed; no discrepancy to reconcile).

postinstall no longer symlinks libsodium with `ln -sf ... || true`, which
silently no-opped on Windows and left a runtime ERR_MODULE_NOT_FOUND.
scripts/link-libsodium.mjs copies the file cross-platform instead, logs one
line, and exits non-zero on genuine failure.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-31 17:21:17 +02:00

33 lines
757 B
JSON

{
"name": "@apexfusion/vector-mcp-builder",
"version": "0.1.0",
"private": false,
"type": "module",
"description": "MCP server for Vector - AI agent interface for the Apex Fusion eUTXO L2",
"bin": {
"vector-mcp-builder": "./build/index.js"
},
"files": [
"build"
],
"scripts": {
"build": "tsup && chmod +x build/index.js",
"start": "node build/index.js"
},
"dependencies": {
"@aws-sdk/client-s3": "^3.1027.0",
"@lucid-evolution/lucid": "^0.4.29",
"@modelcontextprotocol/sdk": "^1.4.1",
"@noble/hashes": "^1.7.1",
"cross-fetch": "^4.0.0",
"dotenv": "^16.4.5",
"zod": "^3.24.1"
},
"devDependencies": {
"@apexfusion/vector-mcp-shared": "*"
},
"engines": {
"node": ">=22"
}
}