Summary
Deno's default resolver rejects a freshly-published stash / @cipherstash/* rc release. The workaround is "nodeModulesDir": "manual" in deno.json, but nothing in the repo's docs or skills says so, and the failure surfaces as an opaque resolution error at import time.
Source
rc.3 skilltester run (2026-07-19/20), finding M5 (major — "smaller sharp edges that each cost real time"). Hit on the supabase-edge surface.
Impact
Cost real time on the surface that is already the hardest in the matrix (supabase-edge was the only FAIL of the run, and the only PARTIAL→PASS story of rc.3). Anyone starting a Deno/edge integration during an rc window hits it before writing a line of encryption code.
Not verified in tree
This is a Deno resolver behaviour rather than a defect in this repo's code, so there is nothing here to grep. Recording it as reported from the run; the fix is documentation.
Proposed fix
Document it where a Deno user will actually be standing:
A one-line deno.json snippet plus the reason (rc packages aren't in the resolver's expected state yet) is enough.
Summary
Deno's default resolver rejects a freshly-published
stash/@cipherstash/*rc release. The workaround is"nodeModulesDir": "manual"indeno.json, but nothing in the repo's docs or skills says so, and the failure surfaces as an opaque resolution error at import time.Source
rc.3 skilltester run (2026-07-19/20), finding M5 (major — "smaller sharp edges that each cost real time"). Hit on the
supabase-edgesurface.Impact
Cost real time on the surface that is already the hardest in the matrix (
supabase-edgewas the only FAIL of the run, and the only PARTIAL→PASS story of rc.3). Anyone starting a Deno/edge integration during an rc window hits it before writing a line of encryption code.Not verified in tree
This is a Deno resolver behaviour rather than a defect in this repo's code, so there is nothing here to grep. Recording it as reported from the run; the fix is documentation.
Proposed fix
Document it where a Deno user will actually be standing:
wasm-inline/ edge section of the relevant skill (stash-encryption, and whichever skill covers the edge runtime — see Document raw-SQL EQL v3 querying: encryptQuery term + ::eql_v3.query_<domain> cast (no-ORM surfaces) #664's sibling gap for the Deno/edge recipe).A one-line
deno.jsonsnippet plus the reason (rc packages aren't in the resolver's expected state yet) is enough.