react 19: the Dependabot halves cannot resolve alone, so the bump needs one combined PR
Maintainers usually reply within 4 days
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, react, typescript
- Domain
- build-system, frontend
Research direction
Start in website/package.json, then check website/package-lock.json and .github/workflows/deploy.yml; the two failing Dependabot halves are #401/#402 and explain why an unmerged lockfile breaks the Pages deploy. In website, bump react, react-dom and @types/react-dom, regenerate the lockfile with npm install, then verify with npm ci and npm run build. Done means the combined PR installs cleanly and the build passes; leave the stale yarn packageManager/resolutions cleanup for a separate change.
Written by the indexing model from the issue text.
Description
Dependabot opened the react 19 major as two PRs, and neither can pass on its own:
- #401 bumps
react18.3.1 to 19.3.1 - #402 bumps
react-domand@types/react-domto 19.3.1 / 19.3.0
Each half breaks the other's peer requirement, so both fail npm ci with ERESOLVE:
#402: Found: [email protected]
Could not resolve dependency: peer react@^19.3.1 from [email protected]
#401: Found: [email protected]
Could not resolve dependency: peer react-dom@^18.3.1 from [email protected]
Merging them one after the other does not fix it either. deploy.yml runs on every push to main, so between the two merges the tracked lockfile does not resolve, the build job fails, and the Pages deploy is skipped. Any PR opened in that window inherits the same broken lockfile.
Proposed fix
One PR that takes the peer set together, with a regenerated lockfile:
reactandreact-domto^19.3.1@types/react-domto^19.3.0(19.3.1 does not exist)
Verified locally against main at 973801b:
npm installwith the bumped versions: 1409 packages, no ERESOLVEnpm ciagainst the regeneratedwebsite/package-lock.json: exit 0npm run build: SUCCESS, static files generated
@docusaurus/core 3.10.2 declares react ^18.0.0 || ^19.0.0, so 19 is inside the supported range. The @slorber/react-helmet-async alias it depends on prints a peer warning capped at react 18, and the install still exits 0.
Related, separate
website/package.json still carries packageManager: [email protected] and a resolutions block pinning react and react-dom to ^18.3.1, both stale since the repo standardised on npm. A yarn install would put react 18 back. npm ignores both, so this does not block the bump, but it should be cleaned up in its own change.
Also worth considering: a groups entry in .github/dependabot.yml covering the peer set, so the next react major arrives as one PR instead of two unresolvable halves.
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 24
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 16
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from IntersectMBO/developer-experience
-
Rename the q4-2025 sesion-notes folder to session-notes, and keep its URL workingPossibly taken @IanoNjuguna claimed this today. Opendocumentation Low Priority
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
IntersectMBO/developer-experience#406 ·
Maintainers usually reply within 4 days
-
Document colour roles in the brand baseline, and resolve the gradient and alpha restrictions it contradictsPossibly taken A pull request linked to this issue is open or already merged. Opendocumentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
IntersectMBO/developer-experience#376 ·
Maintainers usually reply within 4 days
-
documentation pinned
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
IntersectMBO/developer-experience#363 · 1 comment ·
Maintainers usually reply within 4 days
-
documentation pinned
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
IntersectMBO/developer-experience#362 · 1 comment ·
Maintainers usually reply within 4 days
-
documentation pinned
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
IntersectMBO/developer-experience#360 · 1 comment ·
Maintainers usually reply within 4 days
All issues in IntersectMBO/developer-experience
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Update project links after the repository renamesPossibly taken @JonathanTSilva claimed this today. Openai-generated priority: p2 size: xs type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
JonathanTSilva/jts-website#119 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
promplate/code-review#158 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
[Docs] CONTRIBUTING points the Backend Remake milestone at a branch that does not existPossibly taken @franpts2 claimed this today. Opendocs
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 3 days