A build artifact is a file or packaged output generated by compiling, bundling, or otherwise building software. Every build produces artifacts whose size can be measured byte-for-byte and compared with earlier builds, making size a performance dimension available before release. section 8.0
Artifact growth creates operational costs: oversized outputs download more slowly, deploy more slowly, and start more slowly. Small dependency and cache increases can accumulate unnoticed until diagnosing the problem becomes difficult because later changes obscure the cause. section 8.0 section 8.6
Inspect artifacts according to the platform and packaging path:
- Visualize web bundles to locate large libraries, dependencies, and code that bundlers cannot remove because of older module formats. section 8.6
- Inspect backend container layers for caches, build tools, unused packages, and accumulated indirect dependencies left in the final image. section 8.6
- Audit mobile assets and release sizes; App Thinning and Android App Bundles deliver device-specific content but do not remove the need for tracking. section 8.6
- Account for framework overhead in desktop applications; Electron can establish a 120–150MB size floor before application code is added. section 8.6
Catch growth at the build
A developer adds a dependency and notices that the build output has grown. Comparing the artifact immediately and investigating the dependency preserves context; waiting weeks makes the cause harder to isolate and the fix more expensive. section 8.0

