Analyzing Backend Bundle

Use when analyzing the server/desktop backend bundle — "what does the server load at startup?", "is <dependency> lazy on the backend?", "why is <package> in the startup set?", "how big is the eager set?", chunk analysis after adding a dynamic-import seam, backend memory profiling (RSS, retained script source, heap), or any before/after comparison for backend lazy-loading. Records what a bundle actually loads at boot, joins it with the esbuild metafile, and explains why each package is eager. Don't write a new throwaway module-hook logger, metafile joiner, or heap-snapshot parser — all already live here.

triliumnext Updated 38.9k repo stars
Trilium Screenshot

File contents

triliumnext/trilium commit 997d1cd10a

Frequently asked questions

npx get-skill add triliumnext/analyzing-backend-bundle