Analyze dependencies for deno compile

Is there a way to analyze the dependencies that is added when running deno compile? My compiled binary is close to 300mb, and I would want to see what the largest dependencies are.
R
ry26d ago
@halvardssm we don't have tooling to deconstruct a binary. you might try deno info on your program before you deno compile that might give some indication. if we were to add tooling around deno compile what would you want to look like?
K
kittyamazing26d ago
Hi @ry ! deno info work well enough for my usecase, thanks! For tooling around deno compile I would love to see an --analyze flag that could be passed to output something similar to esbuilds analyze.
tmp.js ───────────────────────────────────────────────────────────────── 1.1mb ─ 100.0%
└ ../tmp.mjs ─ 1.1mb ── 99.9%
tmp.js ───────────────────────────────────────────────────────────────── 1.1mb ─ 100.0%
└ ../tmp.mjs ─ 1.1mb ── 99.9%