Validate @toolbox-web/grid index.js bundle size against raw and gzipped limits.
npx skills add https://github.com/OysteinAmundsen/toolbox --skill bundle-check
Please help me install this Agent Skill. Skill: bundle-check Source: https://github.com/OysteinAmundsen/toolbox/tree/main/.github/skills/bundle-check Command: npx skills add https://github.com/OysteinAmundsen/toolbox --skill bundle-check
Check that the @toolbox-web/grid build stays within bundle size budget (index.js ≤170 kB raw, ≤50 kB gzipped hard limit, ≤45 kB gzipped soft warning). Run after any code change that could affect bundle size.
Run the bundle-check after any change to the grid code to verify the index.js size stays within the defined budgets.
High-intent search queries and answers about installing and using this skill.
You can enforce bundle size limits in CI by running a post-build validation that checks raw and gzipped output against predefined thresholds, reporting violations when limits are exceeded. This automates regression detection for code changes.
A practical gzipped bundle size limit for a web grid component is 50 kB hard, with a 45 kB soft warning threshold to catch regressions early. Raw size should stay under 170 kB to maintain performance.
Check if code changes increased the bundle size by running an automated post-build verification step that measures raw and gzipped output against established budgets. It flags any breaches caused by the new code changes.
Yes, bundle size automation works across both local and CI builds by validating the index.js file size against raw and gzipped limits after the build process. It ensures consistent size enforcement in all environments.
When your bundle size exceeds the budget limit, follow the provided remediation steps to tighten the bundle size and reduce the output. The check flags hard and warning threshold breaches to guide your optimization.
el-feoWrite maintainable Jest unit tests for JavaScript and TypeScript projects.
berkcangumusisikAnalyze frontend bundles to identify size growth and optimization opportunities.
tsuji-tomonoriAutomate accessibility testing in CI/CD pipelines with quality gates.
0xtaoistPrune unused dependencies and apply tree-shaking to reduce JavaScript/TypeScript bundle sizes.
