Add bundle size monitoring with size-limit#43
Conversation
Measures gzipped (brotli) size of each published package's public API surface using esbuild via size-limit. Workflow posts/updates a PR comment via andresz1/size-limit-action. Entries point at TS sources with peer deps marked as ignored so we measure what the library itself contributes.
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: ASSERTIVE Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
View your CI Pipeline Execution ↗ for commit b647f5f
☁️ Nx Cloud last updated this comment at |
Summary
This PR adds automated bundle size monitoring to the project using
size-limit. A GitHub Actions workflow will now check bundle sizes on pull requests to help prevent unintended size regressions.Key Changes
Added size-limit configuration (
.size-limit.json): Defines bundle size limits for all four packages:effect-firebase@effect-firebase/admin@effect-firebase/client@effect-firebase/mockAdded GitHub Actions workflow (
.github/workflows/size.yml): Automatically runs on pull requests tomainandnextbranchessize-limit-actionto check bundle sizesUpdated package.json:
sizenpm script that runssize-limitsize-limitand@size-limit/preset-small-libas dev dependenciesImplementation Details
.nvmrcNode version specificationhttps://claude.ai/code/session_01PSFXZZ7dMnxFc9ofxTDt4u