absolute analyze

Break down what your build ships — by category — and catch size regressions before they land.

#Usage

absolute analyze reads your build manifest and groups every shipped asset into categories — page bundles, hydration entries, client bundles, islands, shared chunks, and CSS — with a running total. It reads from disk, so it works on any build without a server. Add --json for the raw per-asset sizes.

BASH

# Bundle size breakdown by category (pages, islands, chunks, CSS)
absolute analyze

# Record a baseline; later runs show the diff (+/- per category)
absolute analyze --save

#Size diffs in CI

Run absolute analyze --save to record a baseline (.absolute-size-baseline.json, safe to commit). After that, every analyze shows the delta per category plus the biggest individual changes — so a pull request can surface Dashboard +4 KB instead of letting bundle bloat creep in unnoticed. Pair it with ls --budget to fail CI on a hard ceiling.

absolute analyze

$ absolute analyze
  Pages          312 KB   +4 KB
  Hydration      180 KB   —
  Islands        165 KB   —
  Shared chunks  410 KB   -2 KB
  CSS            18 KB    —
  ──────────────────────────
  Total          1.1 MB   +2 KB

  Biggest changes
    +4 KB   Dashboard
    -2 KB   Chunk5wc6pv6k

  vs baseline .absolute-size-baseline.json

PreviousBuild output NextRoutes