Being able to see at a glance what the raw and minimised diff lines are for each chunk file can help in determining how much effort reviewing a build will take. If we can copy/paste this as markdown (or insert it directly into the default CHANGELOG entry), then we can also give some useful stats for a build even if we do no deeper manual analysis.
eg.
- TODO: The following files haven't been deeply reviewed:
- `unpacked/_next/static/chunks/101.js` (`931` lines)
- `unpacked/_next/static/chunks/2637.js` (`5290` lines)
- `unpacked/_next/static/chunks/3032.js` (`150,855` lines)
- `unpacked/_next/static/chunks/30750f44.js` (diff: `45,368` lines, minimised diff: `17,151` lines)
- `unpacked/_next/static/chunks/3453.js` (`403` lines)
- Seem to be a bunch of images, likely related to image generation styling or similar.
- `unpacked/_next/static/chunks/3472.js` (`320` lines)
- Statsig, Feature Gates, Experimental Gates, etc
- `unpacked/_next/static/chunks/3842.js` (`755` lines)
- `unpacked/_next/static/chunks/3a34cc27.js` (diff: `4373` lines, minimised diff: `1633` lines)
- `unpacked/_next/static/chunks/4114.js` (diff: `1411` lines, minimised diff: `1373` lines)
Being able to see at a glance what the raw and minimised diff lines are for each chunk file can help in determining how much effort reviewing a build will take. If we can copy/paste this as markdown (or insert it directly into the default CHANGELOG entry), then we can also give some useful stats for a build even if we do no deeper manual analysis.
eg.