Refine bundle size report comments - #870
Conversation
Size budgetsMeasured head:
Repository writers, including the PR author, can accept current soft-budget breaches with a reason: Use one command per platform; several lines can share a comment. Post after this report is ready for the current head. Commands in edited comments are not accepted. Acceptance applies to each currently exceeded metric up to its recorded size. Further growth or a newly exceeded metric needs fresh acceptance. Hard-budget increases require a reviewed change to Bundle and package sizeWeb bundle sizes cover shipped runtime JavaScript. Package sizes cover the full published archive, including any source maps, declarations, and documentation it contains.
Web package files (uncompressed)These are uncompressed file sizes; they do not sum to the compressed package size above.
React Native package files (uncompressed)These are uncompressed file sizes; they do not sum to the compressed package size above.
Android package files (uncompressed)These are uncompressed file sizes; they do not sum to the compressed package size above.
How sizes are measuredMeasured from the PR base SHA and PR head SHA. Web bundle rows sum shipped |
|
↑ heads up the changes will only apply when this PR lands in main |
Size reports show commit SHAs and acceptance instructions even when budgets pass. Remove the visible SHA line, show acceptance guidance only for unresolved soft or hard budget breaches, and add status emojis to the results.
Rename the heading to Bundle Size Budgets and reduce its table to four columns: Budget, Size, Limits, and Result. Combine platform and measurement labels, show the current size with its change, and put soft and hard limits together. Keep compression labels explicit and show changes smaller than 1 KiB in bytes. Base sizes remain in the detailed measurement table.
Collapse the measurement explanation under How sizes are measured. Preserve the budget rules and hidden acceptance state.