deco-site-memory-debugging
Installation
SKILL.md
Deco Site Memory Debugging
Two runtime targets, two different diagnostic stories — pick the section that matches how the site is deployed.
| Site built on... | Runtime | Diagnostic path |
|---|---|---|
@decocms/tanstack |
Cloudflare Workers (wrangler deploy) |
No persistent process to attach a debugger to. Diagnose via tail-worker-captured exceededMemory/exceededCpu outcomes in ClickHouse, wrangler tail, and local repro under wrangler dev. See Part 1 below. |
@decocms/nextjs |
Node/RSC | Real CDP flow via node --inspect — same underlying methodology as the old Deno flow (force GC, heap snapshot, Response-leak detection), different API surface. See Part 2 below, cdp-connection.md, memory-analysis.md. |
Superseded content. This skill previously assumed Deno-on-Kubernetes (
Deno.memoryUsage(), CDP overkubectl port-forwardinto a pod's port 9229, Deno-specific V8 inspector quirks). That deployment model does not exist for current blocks sites — neither Cloudflare Workers nor Node/RSC exposesDeno.memoryUsage()or lives in akubectl-managed pod.cdp-connection.mdandmemory-analysis.mdare now written for Node/RSC (@decocms/nextjs) specifically; if you're debugging a legacy Deno/Fresh/Knative site outside this package split, pull the Deno-flow version of this skill from git history instead of following the current files.