modelcontextprotocol/inspector
Watch
1
0
Fork
You've already forked inspector
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2

docs(scripts): correct the deleted-source caveat — it is silent, not loud

Browse source 
Round 3's suppressed finding, and it corrects a claim of mine that was
simply wrong. The header said a deleted source file's stale `.js` produces
"a loud failure rather than a silent one — an import of a removed module
fails at the consumer". It does not: the stale file is still there, so the
post-build existence checks pass against it and anything still importing
that module keeps silently running the old code. That is the SAME failure
class this PR exists to close, described as though it were the opposite.

Rewritten in the helper header and AGENTS.md to say the unconditional build
does not cover deletion, and to make `rm -rf test-servers/build` after a
delete or rename an instruction rather than an aside — which is now a real
clean, since the tsbuildinfo was pinned inside build/ in 8d19346.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JTHVxSu8AUgHRLvo1ntZ8H
Signed-off-by: cliffhall <cliff@futurescale.com>
This commit is contained in:
cliffhall 2026-08-25 01:37:40 -04:00
commit 3222537e73
1 changed files with 19 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

11
AGENTS.md
View file

@ -266,9 +266,14 @@ v2/main/
│ # silently drove the previous fixture — reported not as
│ # staleness but as a product failure in whatever the
│ # smoke was checking. Unconditional emit is still not a
│ # clean: a DELETED src file leaves its stale `.js`
│ # behind, so `rm -rf test-servers/build` after one —
│ # #2111;
│ # clean, and that is the one hole it does NOT close: a
│ # DELETED src file leaves its stale `.js` behind, the
│ # existence checks pass against it, and anything still
│ # importing that module SILENTLY runs the old code — the
│ # same failure class. So `rm -rf test-servers/build`
│ # after deleting or renaming a source file; the
│ # `.tsbuildinfo` is pinned inside `build/` so that
│ # clean actually invalidates the cache — #2111;
│ # resolve-node-bin.mjs resolves a
│ # package's bin through its own package.json, so the
│ # verify/smoke scripts spawn it with `process.execPath`