VibedByKaKi/t3-code-android-nightly
1
0
Fork 0
mirror of https://github.com/VibedByKaKi/t3-code-android-nightly.git synced 2026-10-11 21:01:16 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions 5
t3-code-android-nightly/.repos/effect-smol/.agents/skills/bundle-analysis/SKILL.md
Julius Marminge e3c85ead63
chore(refs): sync Effect and Alchemy references to rc.115 and beta.78 (#12327) 
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2026-09-17 23:21:25 -07:00

1.4 KiB
Raw Permalink Blame History

name description
bundle-analysis Bundle analysis. Use when measuring current bundle size, comparing stable or selected fixtures, inspecting composition, or cleaning retained comparison state.

Read packages/tools/bundle/README.md, then select one workflow:

  • Stable comparison: pnpm bundle-compare <base-ref>. Use HEAD~1 for the latest commit. Read tmp/bundle-stats.txt and report non-zero differences.
  • Selected comparison: pnpm bundle-compare-selected --base <ref> scratchpad/<fixture>.ts. Use only user-named or investigation-local fixtures; keep temporary fixtures out of the stable corpus.
  • Composition: pnpm bundle-analyze scratchpad/<fixture>.ts. Read raw data first and report the largest modules, dependency groups, and surprising inclusions. Its readable-name output is not an exact size measurement.
  • Current size: Build immediately before the direct bundle report so Effect packages resolve from current dist output.
  • Cleanup: Stable comparisons retain tmp/bundle-base for reuse unless cleanup is requested. Remove selected-comparison state retained with --keep-base after its final use. Verify cleanup without disturbing unrelated worktrees.

The task is complete when the selected artifact is inspected, requested size or composition findings are reported, generated paths are named, and comparison state follows the selected workflow's retention policy.