ai/size-limit

Calculate the real cost to run your JS app or lib to keep good performance. Show error in pull request if the cost exceeds the limit.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 32 minutes ago
Added to GitGenius on September 9th, 2026
Created on June 25th, 2017
Open Issues & Pull Requests: 26 (+0)
GitHub issues: Enabled
Number of forks: 1,759
Total Stargazers: 6,944 (+0)
Total Subscribers: 37 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.3 hours
Mean response time: 3.4 hours
90th percentile: 9.1 hours
Tracked items: 12

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: 775 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

Size Limit is a performance budget tool for JavaScript that checks every commit on CI, calculates the real cost of your JS for end-users, and throws an error if the cost exceeds the limit.

The tool solves the problem of uncontrolled bundle growth by measuring the actual performance impact of code changes rather than just file size. It calculates execution time in the browser, accounting for download speed and parsing overhead, which provides a more meaningful metric than bytes alone. The approach works by integrating into CI systems like GitHub Actions and Circle CI to automatically check pull requests, and it includes all dependencies and polyfills in its calculations. The tool can also analyze why your library has reached a certain size using the --why flag, which leverages Statoscope to show the real cost of internal dependencies.

Size Limit suits both large JavaScript applications with custom bundlers and small npm libraries with many files, thanks to its modular design. It supports ES modules and tree-shaking, ensuring accurate measurements of what actually ships to users. The tool integrates directly into pull request workflows, posting bundle size changes as comments so developers see the impact immediately. This approach is particularly valuable for library maintainers who need to prevent accidental bloat and for teams maintaining performance budgets across large applications.

The project shows consistent maintenance with regular updates addressing both bug fixes and feature enhancements. Development activity demonstrates responsiveness to user issues and pull requests, with a focus on keeping the tool reliable for CI integration. The codebase maintains compatibility with multiple CI platforms and bundler configurations, indicating attention to the diverse needs of its user base.