Track build output size and fail CI if it increases too much

Open
#2,936 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
build-system, ci-cd, performance

Research direction

Start by locating the build command and CI configuration that produce and validate the bundle size. Define a committed size limit, decide whether the root chunk is tracked separately, and verify that normal feature growth requires deliberate threshold updates while unintended increases fail CI.

Written by the indexing model from the issue text.

Description

tools

I've seen libraries do this, where they have a file saying a max allowed bundle size, and you have to increase it manually when the bundle gets bigger. This makes sure there are no accidental large bundle size increases like the one I caught in https://github.com/oxidecomputer/console/pull/2910#issuecomment-3403530384. Unlike some libraries, we expect our total size to be going up regularly as we add more pages and features. That could just mean we increment the max in bigger chunks rather than incrementing it the minimum possible to let the test pass. We could also treat the root chunk separately since it's the thing that users load immediately.

Dominant language
TypeScript
Stars
228
Forks
22
Avg merge
19h 42m
Merged PRs (30d)
32

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from oxidecomputer/console

All issues in oxidecomputer/console

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.