Bump Size Limit
- 12 installs
- 8.7k repo stars
- Updated August 4, 2026
- getsentry/sentry-javascript
bump-size-limit updates .size-limit.js when bundle CI fails.
About
The bump-size-limit skill fixes failing size-limit GitHub Action checks. Workflow runs yarn build for up-to-date CDN artifacts, then yarn test:size-limit JSON output, filters passed false entries, rounds actual bytes up to next full kilobyte for new limit strings, updates only failed scenarios in root .size-limit.js, and re-runs until green. Avoid touching passing limits. Dev builds are insufficient because measurements need production bundles from packages/browser/build/bundles. Requires full yarn build before measuring bundles. Parses yarn test:size-limit JSON for failures. Rounds actual size up to next KB limit string. Updates only failed scenarios in .size-limit.js. Re-runs test:size-limit to verify pass. Passing size-limit run with conservatively bumped thresholds. User mentions size limit failure or bumpSizeLimit request. Maintainers responding to size-limit CI failures on SDK PRs. Ship-phase testing work unblocking bundle size CI failures. DevOps subphase fits artifact size gate maintenance.
- Requires full yarn build before measuring bundles.
- Parses yarn test:size-limit JSON for failures.
- Rounds actual size up to next KB limit string.
- Updates only failed scenarios in .size-limit.js.
- Re-runs test:size-limit to verify pass.
Bump Size Limit by the numbers
- 12 all-time installs (skills.sh)
- Ranked #977 of 1,435 DevOps & CI/CD skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
bump-size-limit capabilities & compatibility
- Capabilities
- six step workflow from build to verify · kb rounding heuristic example
- Works with
- sentry · github
- Use cases
- ci cd · testing
What bump-size-limit says it does
yarn build
npx skills add https://github.com/getsentry/sentry-javascript --skill bump-size-limitAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 12 |
|---|---|
| repo stars | ★ 8.7k |
| Last updated | August 4, 2026 |
| Repository | getsentry/sentry-javascript ↗ |
How do I fix failing size-limit CI in sentry-javascript?
Bump .size-limit.js thresholds when size-limit CI fails after full yarn build measurement.
Who is it for?
Maintainers responding to size-limit CI failures on SDK PRs.
Skip if: Skip when bundles genuinely need size reduction not limit bump.
When should I use this skill?
User mentions size limit failure or bumpSizeLimit request.
What you get
Passing size-limit run with conservatively bumped thresholds.
Files
Bump Size Limit
When the size-limit GitHub Action fails, it means one or more bundle scenarios exceed their configured byte thresholds in .size-limit.js. This skill walks through building, measuring, and bumping only the limits that need it.
Workflow
Step 1: Build all packages (including CDN bundles)
A full build is required because size-limit measures the actual compiled artifacts.
yarn buildThis takes a few minutes. CDN bundles in packages/browser/build/bundles/ must be up to date — a dev build is not sufficient.
Step 2: Run the size check in JSON mode
yarn test:size-limitThe JSON output is an array of objects. Each object has:
name— the scenario labelpassed— whether it's within the limitsize— actual size in bytessizeLimit— configured limit in bytes
Step 3: Identify failed scenarios
Filter for entries where "passed": false. These are the only ones that need bumping.
Step 4: Calculate new limits
For each failed scenario, round the actual size up to the next full KB (1 KB = 1000 bytes in this context, matching how size-limit interprets the limits in .size-limit.js).
Example: If actual size is 129,127 bytes, the new limit is 130 KB (i.e. 130,000 bytes).
The heuristic is intentionally conservative — it gives just enough headroom without inflating limits unnecessarily.
Step 5: Update .size-limit.js
Open .size-limit.js at the repository root and update the limit field for each failed scenario. Limits are strings like '130 KB'.
Only change limits for scenarios that actually failed. Do not touch passing scenarios.
Step 6: Verify the fix
Re-run size-limit to confirm everything passes:
yarn test:size-limitIf any scenario still fails (e.g., due to rounding edge cases), bump that specific limit by another 1 KB and re-run.
Related skills
Azure DeploySafely execute production deployments of already-prepared applications to Microsoft Azure.485k1.3kAzure ValidateRun deep pre-deployment checks on Azure configuration, infrastructure definitions, RBAC roles, and managed identities before pushing to production.485k1.3k
Github Actions DocsGet precise, docs-grounded answers about GitHub Actions workflows, syntax, security, and migration instead of relying on stale knowledge.275k72
Setup Pre CommitAutomatically run Prettier, type checking, and tests on every commit via Husky and lint-staged.170k199k
Deploy To VercelSafely turn any local project into a live Vercel preview with one instruction.99.3k29.7kVercel Cli With TokensDeploy projects to Vercel from agents and scripts using token authentication instead of interactive browser login.74.6k29.7kFAQ
What does bump-size-limit do?
bump-size-limit updates .size-limit.js when bundle CI fails.
When should I use bump-size-limit?
User mentions size limit failure or bumpSizeLimit request.
Is this skill safe to install?
Review the Security Audits panel on this page before installing in production.