siddharthkp/bundlesize

Keep your bundle size in check

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 48 minutes ago
Added to GitGenius on September 15th, 2026
Created on June 27th, 2017
Open Issues & Pull Requests: 83 (+0)
GitHub issues: Enabled
Number of forks: 176
Total Stargazers: 4,470 (+0)
Total Subscribers: 29 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.0 days
Mean response time: 593.7 days
90th percentile: 2316.9 days
Tracked items: 4

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 538 days
Stale 30+ days: 4
Stale 90+ days: 4

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

bundlesize is a build tool that enforces bundle size limits on your JavaScript artifacts.

The tool solves the problem of unintended bundle bloat by allowing you to specify maximum size thresholds for your build outputs and failing the build if those thresholds are exceeded. It works by accepting a configuration of files to monitor, compressing them (gzip by default), and comparing their sizes against your defined limits. The tool supports fuzzy glob patterns to match files with unpredictable names like those with content hashes, making it compatible with build systems like create-react-app and Next.js.

bundlesize suits projects where bundle size matters to performance and you want automated enforcement in your CI pipeline. It integrates with GitHub pull requests to display size check results directly on commits when used with Travis CI, CircleCI, Wercker, or Drone. The tool offers flexibility in compression methods, allowing you to specify brotli compression per file or disable compression entirely if needed. Configuration lives in package.json or a separate bundlesize.config.json file, keeping setup minimal.

The project maintains active engagement with its issue tracker and pull requests, responding to user questions and reviewing contributions. Development includes regular updates to dependencies and bug fixes addressing edge cases in file matching and CI integration. The tool receives ongoing maintenance to support new CI platforms and compression standards as they emerge.