fix(playground): bump main entrypoint chunk-size limit 1800 → 1850 KB#23223
Merged
Conversation
ledwards2225
approved these changes
May 12, 2026
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
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.
What
Bumps the hard chunk-size cap on the playground's main entrypoint chunk (
assets/index-*.js) inplayground/vite.config.tsfrom 1800 KB → 1850 KB, plus a bump-log entry.Why
The
merge-train/barretenbergPR (#23137) is repeatedly failing in the merge queue on a deterministicyarn buildfailure inplayground/:(merge-queue log:
ci.aztec-labs.com/a34536031aaca0b9)The 1800 KB limit was only raised four days ago (#23107, 1750 → 1800). The merge train bundles further bb-side changes on top of
next— notablyfeat: multi-app kernel circuits (#23076)— which nudged bb.js ~1.3 KB past the just-raised ceiling. It will fail on every queue attempt until the cap is raised. 1850 KB restores a small amount of headroom.Note
This lands the bump on
next. To unblock #23137 immediately,nextneeds to be re-merged intomerge-train/barretenbergonce this merges (or the same one-liner can be applied directly on that branch — note that branch's earlier conflict resolution dropped one of the two=> 1800bump-log comment lines, so expect a trivial conflict on the comment block when re-merging).No behavior change; CI build only.
Created by claudebox · group:
slackbot