Repository navigation
Conversation
Measure the freshly built index_bg.wasm (raw, gzip -9 and brotli -11) in the publish check job, compare it with the baseline recorded in e2e/wasm-size/budget.json, and fail above the approved budget. The table goes to the step summary and a JSON artifact so growth stays visible on every run even within the budget. Refs #683 (INF-26) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 🚀 New features to boost your workflow:
|
This was referenced Nov 15, 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.
Summary
INF-26: WASM 크기에 추적 가능한 기준선과 예산(budget)이 없던 문제를 해결합니다.
e2e/wasm-size/check.mjs: 빌드된bindings/devup-ui-wasm/pkg/index_bg.wasm의 raw / gzip(-9) / brotli(-11) 크기를 측정하고,e2e/wasm-size/budget.json의 기준선(baseline)과 비교해 예산을 넘으면 실패합니다.GITHUB_STEP_SUMMARY에, JSON 결과는WASM_SIZE_OUTPUT경로에 기록되어 예산 이내의 증가도 매 실행마다 보입니다.budget.json: 현재 main 소스로 빌드한 WASM(raw 7,060,664 / gzip 2,548,140 / brotli 1,783,230 바이트)을 기준선으로, 약 5.5% 여유를 둔 값(7,450,000 / 2,690,000 / 1,885,000)을 예산으로 기록했습니다. 이슈 본문의 5,387,595 바이트는 Boa 도입 이전 수치라 현재와 맞지 않습니다.publish검사 job의bun run build직후에Check the WASM size budget단계와wasm-sizeartifact 업로드 단계를 추가했습니다. release/publish 동작과 secret은 건드리지 않았습니다.check.test.mjs(node --test)를test:bun스크립트에 추가했습니다. 측정, 비교, 보고서, 실패 경로, 기본 budget 파일 사용, 예산이 기준선보다 10% 이상 느슨하지 않은지를 검사합니다.budget.json을 리뷰를 거치는 변경으로 수정합니다(실패 메시지에 안내 포함).packages/*변경이 없어서 changepack은 추가하지 않았습니다.Test plan
node --test e2e/wasm-size/check.test.mjs(7 pass)run()실행 시 예산 이내로 통과 확인bunx prettier --single-quote --no-semi --check e2e/wasm-sizepublishjob의Check the WASM size budget단계 통과와 step summary 확인Refs #683
🤖 Generated with Claude Code