[6.x] Disable reportCompressedSize in Storybook build#14468
Merged
jasonvarga merged 1 commit into6.xfrom Apr 9, 2026
Merged
Conversation
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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.
Summary
reportCompressedSizein the Storybook Vite config to reduce memory usage during production builds.After the Vite 8 upgrade, the Storybook docs build was getting killed by the OOM killer on the deploy server (3.8GB RAM) during the "computing gzip size" phase. This option only controls whether gzip sizes are printed in the build log — it has no effect on the output files.
Test plan
npm run build-storybook-docsstill works🤖 Generated with Claude Code