0.0.15: the stack filter skipped the wrong frames
0.0.14's instrument reported `bare-fs/index.js` three times — which is bare-fs's
RECURSIVE mkdir calling itself, not the caller. `slice(1, 4)` named the failing
primitive, which the message already said, and hid the only thing it did not.
⛔ A FIXED DEPTH IS ALWAYS WRONG when the failing call is recursive: the helper
can produce arbitrarily many internal frames before the caller appears. Filter by
ORIGIN — drop bare-fs, bare-module, bare-path and `bare:` frames — and take the
first four that remain.
Proved before shipping rather than after: a deliberate recursive mkdir failure
now yields the calling file and line, with every bare-fs frame gone.
⚠ Still no fix for the ENOENT itself. The three homedir defaults I already
overrode are all verified present in the shipped bundle, so the fourth caller is
somewhere my greps do not reach — which is exactly what this is for.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
a036255b875a359b972d20376d701338f36acfe0
by plankatron <fleeky@gmail.com> · 2026-09-10T18:29:18.000Z