949a56312a
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>
21 lines
424 B
JSON
21 lines
424 B
JSON
{
|
|
"name": "@apexfusion/vector-mcp-shared",
|
|
"version": "0.1.0",
|
|
"private": true,
|
|
"type": "module",
|
|
"exports": {
|
|
"./tx": "./src/tx.ts",
|
|
"./types": "./src/types.ts",
|
|
"./config": "./src/config.ts",
|
|
"./provider": "./src/provider.ts"
|
|
},
|
|
"dependencies": {
|
|
"@lucid-evolution/lucid": "^0.4.29",
|
|
"@noble/hashes": "^1.7.1",
|
|
"cross-fetch": "^4.0.0"
|
|
},
|
|
"engines": {
|
|
"node": ">=22"
|
|
}
|
|
}
|