Skip to content

chore(deps): react and react-dom to 19.3.0, together #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
webdevsamran merged 1 commit into from
Sep 15, 2026
Merged

chore(deps): react and react-dom to 19.3.0, together #5

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
44 changes: 22 additions & 22 deletions web/package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

8 changes: 4 additions & 4 deletions web/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,15 +12,15 @@
"check:bundle": "node scripts/check-bundle.mjs"
},
"dependencies": {
"react": "19.2.8",
"react-dom": "19.2.8"
"react": "19.3.0",
"react-dom": "19.3.0"
},
"devDependencies": {
"@eslint/js": "^10.0.1",
"@testing-library/jest-dom": "^7.0.1",
"@testing-library/react": "^16.3.3",
"@types/react": "^19.2.18",
"@types/react-dom": "^19.2.7",
"@types/react": "^19.3.0",
"@types/react-dom": "^19.3.0",
"@vitejs/plugin-react": "^6.1.1",
"eslint": "^10.9.1",
"jsdom": "^30.0.1",
Expand Down
24 changes: 17 additions & 7 deletions web/scripts/check-bundle.mjs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,14 +17,24 @@ const GROUPS = ['overview', 'contract', 'testing', 'runtime', 'agents', 'team']
/* Headroom over the measured entry chunk: enough that ordinary feature work
* does not trip it, tight enough that an un-split build does.
*
* Raised once, from 210,000, when the agent-governance page group took the
* Raised from 210,000 to 220,000 when the agent-governance page group took the
* entry to 205.7 kB and left 4 kB of room -- less than one feature. The plan
* that called for this raise proposed 260,000, and that number would have
* been a mistake: an un-split build of this app is around 240 kB, so a
* 260,000 budget would pass the exact failure the check exists to catch. The
* assertion below now derives that ceiling from the build itself rather than
* trusting either number. */
const ENTRY_BUDGET_BYTES = 220_000
* behind that raise proposed 260,000, and at the time that would have been a
* mistake: an un-split build then weighed about 240 kB, so a 260,000 budget
* would have passed the exact failure this check exists to catch.
*
* Raised again to 260,000 for React 19.3.0, which added 29,273 B to the entry
* on its own (214,558 -> 243,831 B) with no source change. The number that was
* wrong before is right now, and only because the app grew: the assertion
* below derives the un-split weight from the build rather than from memory,
* and it is 301,858 B. So 260,000 still sits 42 kB under the point where this
* check would stop being able to tell a split build from an un-split one, and
* leaves ~16 kB for ordinary work.
*
* That derived assertion is the one that matters. If a future raise pushes
* this constant up to meet it, the answer is not a bigger number -- it is that
* the shell has started carrying page code. */
const ENTRY_BUDGET_BYTES = 260_000

let files
try {
Expand Down
Loading