pi-mono/packages/evals/package.json
Armin Ronacher 6173017a7b fix: drop harness-pi-ai and its legacy registry aliases from evals
The harness declared peer deps on the pre-rename @mariozechner/pi-ai and
@mariozechner/pi-agent-core names, so npm auto-installed our own code from the
registry under an alias. sync-versions bumped those aliases in lockstep, which
made every release fail because the new version is not published yet.

Build the eval harness on createHarness from vitest-evals core instead. The
pi-specific code was already ours; the harness only contributed agent-lifecycle
plumbing and unused tool replay.
2026-07-25 14:36:32 +02:00

18 lines
380 B
JSON

{
"name": "@earendil-works/pi-evals",
"version": "0.82.0",
"private": true,
"type": "module",
"scripts": {
"clean": "shx rm -rf .eval",
"eval": "node scripts/run-evals.mjs"
},
"devDependencies": {
"@earendil-works/pi-coding-agent": "^0.82.0",
"@types/node": "24.12.4",
"shx": "0.4.0",
"typescript": "5.9.3",
"vitest-evals": "0.15.0",
"vitest": "4.1.9"
}
}