Repository navigation
Allow the combined loading UI in the initial bundle budget - #553
Merged
Merged
Conversation
This was referenced Oct 13, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The combined loading UI on main produces 81,543 bytes of initial gzip JavaScript on Linux, exceeding the 81,500-byte cap by 43 bytes and failing every container build. Add 500 bytes to each limit, with a comment explaining the allowance. Application code and budget enforcement are unchanged.
Validation: the exact Linux amd64 Docker build stage passes at 255,943 bytes raw / 81,543 bytes gzip. Formatting, project checks, types, scoped lint, lane audit, and both budget tests pass. This deliberately accepts the measured UI size increase rather than removing the cap.