Uh oh!
There was an error while loading. Please reload this page.
Update react monorepo to v19.2.18 - #16
Conversation
Deploying docs with |
| Latest commit: | 8d8d9ae |
| Status: | 🚫 Build failed. |
d500a06 to
8f9a564Compare8f9a564 to
8d8d9aeCompare8d8d9ae to
9c2e88fComparef168ce8 to
0a13768Compareb28c978 to
d0a2c20Compare2a277f2 to
7739a2bCompare1c52659 to
ba3e90eCompareba3e90e to
eb5703aCompareeb5703a to
d8e9377Compared8e9377 to
72c8caeCompareebfeb96 to
643f7efCompare643f7ef to
8491c21Compare78e99e6 to
3a9ed6cCompareThere was a problem hiding this comment.
Summary
This PR updates React and React DOM from v19.2.0 to v19.2.14, along with updating all related dependencies in the lock files (package-lock.json and yarn.lock). This is a Renovate bot-generated PR for routine dependency maintenance.
Verdict: Needs changes before merging - While the React upgrade itself appears safe, there are significant concerns about the Node.js engine requirement changes that need to be addressed.
Research notes
React 19.2.6 Release Notes: The latest version (19.2.6, released May 6th, 2026) includes "Type hardening and performance improvements" for React Server Components (#36425). No breaking changes mentioned for this patch update.
React 19 Upgrade Guide: According to React's official upgrade guide, React 19 introduces several breaking changes including:
- Removal of
ReactDOM.render,ReactDOM.hydrate(must usecreateRoot/hydrateRoot) - Removal of
propTypesanddefaultPropsfor function components - Removal of string refs, legacy context, and other deprecated APIs
- Changes to error handling (errors no longer re-thrown)
- TypeScript type changes requiring
useRefto have an argument
- Removal of
Docusaurus Compatibility: The lock file changes show Docusaurus packages being updated from 3.8.1 to 3.10.1, which now support
react: ^18.0.0 || ^19.0.0. However, the engine requirement changed fromnode: >=18.0tonode: >=20.0across all Docusaurus packages.Current package.json: Still specifies
"engines": { "node": ">=18.0" }and"packageManager": "yarn@4.9.4"
Suggested next steps
Blocking: Update the
enginesfield inpackage.jsonfrom"node": ">=18.0"to"node": ">=20.0"to match the new Docusaurus requirements, or verify your deployment environment supports Node.js 20+.Non-blocking: Verify the application builds and runs correctly with React 19.2.6, especially if using any deprecated patterns like:
- String refs (
ref="myRef") propTypeson function componentsdefaultPropson function components- Legacy
ReactDOM.render()calls
- String refs (
Testing recommendation: Run the full test suite and verify SSR/hydration works correctly, as React 19 has improved hydration error reporting that may surface previously hidden issues.
General findings
The PR only contains lock file changes (package-lock.json and yarn.lock), with no changes to
package.json. This is appropriate for a dependency version bump where the semver ranges already allow the new versions.The React upgrade path is correct:
^19.0.0in package.json correctly resolves to 19.2.6 (the latest 19.x version).Many transitive dependencies have been updated alongside React, including:
postcss-preset-env: 10.4.0 → 10.6.1node-gyp: 11.5.0 → 12.3.0 (now usesundiciinstead ofmake-fetch-happen)- Various security patches in the ecosystem
Important: If your CI/CD pipeline or production environment runs Node.js 18.x, this PR will break builds after merge due to the Docusaurus engine requirement change to Node.js 20+. This should be verified before merging.
3a9ed6c to
94df8e5CompareThere was a problem hiding this comment.
Summary
This PR updates React-related dependencies from v19.2.0 to v19.2.6 (React/ReactDOM) and @types/react to v19.2.14. The update itself appears safe - the React 19.2.6 release notes indicate only "type hardening and performance improvements" for React Server Components with no breaking changes.
However, there are several issues that need attention before this can be approved:
- Misleading PR title - Claims "v19.2.14" but React itself only goes to 19.2.6
- Version constraint drift - yarn.lock shows changed version ranges (^19.0.0 → ^19.2.6)
- Dual lockfile anti-pattern - Both yarn.lock and package-lock.json committed despite using Yarn
Research notes
- Fetched React 19.2.6 release notes - confirms minor update with type/performance improvements only
- Package.json specifies
"packageManager": "yarn@4.9.4"indicating Yarn Berry is the intended package manager - Yarn lockfile format confirms Yarn 4.x (checksums use
10c0/prefix)
Suggested next steps
- Fix PR title to accurately reflect versions (React 19.2.6, @types/react 19.2.14)
- Investigate why yarn.lock version constraints changed from ^19.0.0 to ^19.2.6 - this suggests either manual editing or transitive dependency forcing resolution
- Remove package-lock.json from version control since project uses Yarn (or configure corepack to prevent npm from generating it)
- Run
yarn installfresh to regenerate clean lockfile with correct version ranges preserved
General findings
Dual lockfile maintenance issue
The repository tracks both yarn.lock and package-lock.json, but package.json explicitly declares "packageManager": "yarn@4.9.4". This creates potential for dependency drift between tools.
Why it matters: Having both lockfiles can lead to inconsistent installations depending on which tool runs first. CI might use one tool while developers use another, causing "works on my machine" issues.
Suggested fix: Add package-lock.json to .gitignore and remove it from the repository. If npm compatibility is needed, consider using yarn install --no-immutable in CI or document which tool is authoritative.
Version constraint preservation in yarn.lock
The diff shows yarn.lock entries changing from "react@npm:^19.0.0" to "react@npm:^19.2.6". Yarn typically preserves the original semver range from package.json in the lockfile key.
Why it matters: This suggests either (a) the lockfile was regenerated with different resolution logic, (b) a transitive dependency is forcing stricter constraints, or (c) manual edits were made. This makes the actual resolved versions opaque to future maintainers.
Suggested fix: Run yarn install with the current package.json to regenerate the lockfile. Verify that version ranges in yarn.lock match what's declared in package.json.
94df8e5 to
3fc03faCompareThere was a problem hiding this comment.
Summary
This PR updates the yarn.lock and package-lock.json files to resolve newer versions of React ecosystem packages. The base package.json dependencies remain unchanged (react@^19.0.0, react-dom@^19.0.0, Docusaurus ^3.9.2), but the lock files now resolve to more recent patch versions.
Verdict: Approved with minor notes - this is a routine dependency resolution update with no breaking changes expected for end users.
Research notes
- React 19.2.x changelog: React 19.2.0 introduced
<Activity>,useEffectEvent,cacheSignal, and various SSR/Suspense improvements. Patch versions 19.2.1-19.2.6 contain bug fixes only. - Docusaurus compatibility: Docusaurus 3.9.2 (current in package.json) supports React 19 per official docs. The resolved
@docusaurus/*packages at ^3.9.2 maintain compatibility with React 19.2.x. - webpack-dev-middleware: Updated from 5.x to 7.x (requires Node >= 18.12, already satisfied by engine constraint
>=18.0). - selfsigned: Major version jump from 2.4.1 to 5.5.0 - internal dev dependency for webpack-dev-server, no user-facing impact.
Suggested next steps
- Verify build locally - Run
yarn install && yarn buildto ensure the new resolved versions don't introduce any type errors or build failures. - Test dev server - The webpack-dev-server and webpack-dev-middleware updates could affect local development; verify
yarn startworks correctly. - Consider pinning React versions - If deterministic builds are critical, consider changing
^19.0.0to an exact version in package.json to prevent future surprises.
General findings
- The PR title "Update react monorepo to v19.2.15" is slightly misleading -
reactandreact-domare updated to 19.2.6, while only@types/reactgoes to 19.2.15. This is normal (type definitions often version independently), but worth clarifying. - No changes to package.json means this is purely a lockfile regeneration, likely from running
yarn installwith updated upstream packages. - All peer dependency ranges appear satisfied - no conflicts detected in the lock file diff.
3fc03fa to
fe17fe1CompareThere was a problem hiding this comment.
Summary
This PR updates lock files (package-lock.json and yarn.lock) to resolve dependency versions, primarily driven by React type definitions updates (@types/react 19.2.2 → 19.2.15, @types/react-dom 19.2.2 → 19.2.3). The changes also pull in updated transitive dependencies including Docusaurus (3.8.1 → 3.9.2/3.10.1), Algolia clients (5.40.x → 5.53.0), and Babel packages (7.27.x/7.28.x → 7.29.7).
Verdict: Needs changes - the package.json engines field should be updated to reflect new Node.js requirements from Docusaurus.
Research notes
- Fetched Docusaurus release notes: Updates from 3.8.1 to 3.10.1 are backward-compatible minor releases with bug fixes and features, no breaking changes for typical documentation site usage.
- Checked npm registry for @types/react: Version 19.2.15 is the latest stable release (published May 2026), updating from 19.2.2. These are TypeScript type definitions from DefinitelyTyped - typically non-breaking.
- CI workflow uses Node.js 22, which satisfies all new engine requirements.
Suggested next steps
- Blocking: Update
package.jsonengines field from"node": ">=18.0"to"node": ">=20.0"to align with Docusaurus 3.9+ requirements. - Consider documenting the Node.js version requirement change in a changelog or migration note if one exists.
- Verify the build succeeds locally with Node 20+ before merging.
General findings
Node.js Engine Requirement Mismatch
Multiple Docusaurus packages (core, bundler, logger, plugin-content-docs, theme-classic, etc.) now specify "engines": { "node": ">=20.0" } in the updated lock files, but package.json still declares "engines": { "node": ">=18.0" }. While the CI uses Node 22 (which is compatible), developers or deployment environments using Node 18 may encounter warnings or failures.
Mixed Package Manager Lock Files
The repository maintains both package-lock.json (npm) and yarn.lock (Yarn). The project explicitly uses Yarn 4.9.4 (per packageManager field and .yarnrc.yml). Having both lock files can lead to divergence if updates are made with different package managers. Consider whether package-lock.json is needed or should be added to .gitignore if only Yarn is used.
PR Title Accuracy
The title "Update react monorepo to v19.2.15" is somewhat misleading - while @types/react is updated to 19.2.15, the PR includes broader dependency updates (Docusaurus, Algolia, Babel). A more accurate title might be "chore(deps): update dependencies" or similar.
General findings (auto-demoted from inline due to pre-validation)
- Blocking
package-lock.json:49— This engines declaration in package.json specifies">=18.0"but the updated Docusaurus dependencies (visible in this diff at multiple locations) now require"node": ">=20.0". This mismatch could cause issues for developers or CI environments running Node 18.- (demoted: line 49 (side=RIGHT) is not part of any diff hunk in package-lock.json)
fe17fe1 to
c4ab7daCompareThere was a problem hiding this comment.
Summary
This PR updates the React-related dependencies in the lock files (yarn.lock and package-lock.json). The commit message states "Update react monorepo to v19.2.16" but the actual React version being resolved is 19.2.7. The package.json continues to specify ^19.0.0 for React packages.
Verdict: Needs clarification before approval - The PR appears to be a routine dependency update from Renovate, but there are discrepancies between the PR title, commit message, and actual versions being installed that should be clarified.
Research notes
I reviewed the React 19 release notes and React 19 Upgrade Guide to identify potential breaking changes:
- JSX Transform: React 19 requires the new JSX transform (introduced in 2020). Most modern setups already have this enabled via Babel/TypeScript configuration.
- Removed deprecated APIs:
propTypes,defaultPropsfor function components, string refs, legacy context,createFactory, module pattern factories, and various ReactDOM methods (render,hydrate,unmountComponentAtNode,findDOMNode). - Error handling changes: Errors in render are no longer re-thrown; new
onUncaughtErrorandonCaughtErrorcallbacks are available. - TypeScript changes:
useRefnow requires an argument, ref callback cleanup functions change typing requirements.
For this Docusaurus site using React 19.0.0 → 19.2.7, the main risk is transitive dependencies that may rely on deprecated React APIs.
Suggested next steps
- Clarify the version discrepancy between PR title (v19.2.15), commit message (v19.2.16), and actual React version (19.2.7)
- Test the build locally with
yarn install && yarn buildto ensure Docusaurus can successfully build with the updated React version - Consider updating package.json to explicitly specify the target React version range if intentional (e.g.,
^19.2.7) - Verify TypeScript compilation passes with the updated
@types/reactand@types/react-dom(19.2.16)
General findings
Version inconsistency in PR metadata
The PR title states "Update react monorepo to v19.2.15" but:
- The commit message says "Update react monorepo to v19.2.16"
- The yarn.lock resolves React to version 19.2.7
- The @types/react resolves to 19.2.16
This suggests the PR title may have been auto-generated incorrectly by Renovate, or there's confusion about which version number refers to which package. For future Renovate PRs, consider configuring Renovate to include more specific version information in the PR title.
Package.json vs lockfile drift
The package.json specifies "react": "^19.0.0" which allows any 19.x version, so the lockfile updating to 19.2.7 is within spec. However, if you want more predictable builds or explicit version tracking, consider:
- Pinning to exact versions:
"react": "19.2.7" - Or using a more specific range:
"react": "^19.2.0"
This would make it clearer what React version the project targets and reduce confusion in PR titles.
Build verification recommended
The CI workflow runs yarn build which should catch most React compatibility issues. However, I recommend manually testing:
- Local dev server with
yarn start - Production build with
yarn build - Preview the built site with
yarn serve
This ensures React 19.2.7 doesn't introduce runtime issues with your Docusaurus components, especially the custom InteractiveOverview component.
c4ab7da to
f9e1b32CompareThere was a problem hiding this comment.
Summary
This PR updates React and React-DOM from 19.2.0 to 19.2.7 via Yarn's semver resolution (package.json specifies ^19.2.7 after the update). The change also updates numerous transitive dependencies including build tools, CSS processors, and server-related packages.
Verdict: Needs minor corrections before merging — see blocking finding about version mismatch.
Research notes
- React 19 Release Notes: React 19 introduced new features like Actions,
useActionState,useOptimistic,use(), ref as prop, form actions, and Server Components. Breaking changes include removal of deprecated APIs (propTypes,defaultPropsfor functions, string refs, legacy context,ReactDOM.render, etc.). - React 19 Upgrade Guide: Provides migration guidance and codemods for breaking changes.
- React Changelog: Versions 19.2.0 → 19.2.7 contain bug fixes primarily for React Server Components (cycle protection, FormData fixes in Server Actions).
- Docusaurus 3.9.x (current version in package.json) supports React 18.x and 19.x according to peer dependency ranges found in lockfile (
react: ">= 16.8.0 < 20.0.0").
Suggested next steps
- Blocking: Fix the version mismatch between PR title ("v19.2.16"), commit message ("v19.2.17"), and actual resolved versions in lockfiles (19.2.7).
- Verify the application builds successfully with
yarn buildafter merging. - Test SSR/hydration behavior if the app uses static site generation or server-side rendering.
- If using any deprecated patterns (string refs,
propTypes,defaultPropsin function components), address them proactively even though React 19 may only warn in some cases.
General findings
Transitive dependency updates warrant attention
Several notable transitive dependency changes:
- node-gyp: 11.5.0 → 12.4.0 (native build tool, should not affect runtime)
- postcss-preset-env: 10.4.0 → 10.6.1 (CSS processing, added new PostCSS plugins)
- svgo: 3.3.2 → 3.3.3 (SVG optimization)
- selfsigned: 2.4.1 → 5.5.0 (major version bump, changed from
node-forgetopkijsfor certificate generation — dev-only dependency) - qs: 6.13.0 → 6.15.2 (query string parsing, minor security/stability fixes)
- send/serve-static/express ecosystem: Multiple packages received patch updates addressing security hardening (e.g.,
encodeurl,http-errors,statusesversion alignment)
These are all indirect dependencies used during build/dev time. Runtime impact should be minimal, but testing is recommended.
No source code changes required
The package.json already declares ^19.0.0 for React, so this update aligns the lockfile with what was already permitted. Assuming the codebase was working on 19.2.0, no code changes should be needed for 19.2.7 since it's a patch release focused on bug fixes.
JSX transform
React 19 requires the new JSX transform. Since the project uses Docusaurus 3.9.x and TypeScript, the Babel/TypeScript configuration should already emit the modern JSX format. If you see warnings about "outdated JSX transform", check your tsconfig.json has "jsx": "react-jsx" or that Babel config includes @babel/preset-react with runtime: 'automatic'.
General findings (auto-demoted from inline due to pre-validation)
- Blocking
yarn.lock:12047— Version specifier inconsistency detected.- (demoted: line 12047 (side=RIGHT) is not part of any diff hunk in yarn.lock)
- Non-blocking
yarn.lock:12052— Peer dependency alignment looks correct.- (demoted: line 12052 (side=RIGHT) is not part of any diff hunk in yarn.lock)
- Non-blocking
yarn.lock:12062— React version update from 19.2.0 to 19.2.7.- (demoted: line 12062 (side=RIGHT) is not part of any diff hunk in yarn.lock)
- Non-blocking
yarn.lock:9380—path-to-regexpupdated from 0.1.12 to 0.1.13.- (demoted: line 9380 (side=RIGHT) is not part of any diff hunk in yarn.lock)
- Non-blocking
yarn.lock:11139— Major version bump forselfsignedfrom 2.4.1 to 5.5.0.- (demoted: line 11139 (side=RIGHT) is not part of any diff hunk in yarn.lock)
- Non-blocking
yarn.lock:10452—qsupdated from 6.13.0 to 6.15.2.- (demoted: line 10452 (side=RIGHT) is not part of any diff hunk in yarn.lock)
f9e1b32 to
79f90a9Compare79f90a9 to
cd06a6dCompare86d10a2 to
02c000bCompare02c000b to
be75d17Comparebe75d17 to
7c70b8bCompare
This PR contains the following updates:
19.2.2→19.2.1819.2.2→19.2.519.2.0→19.2.819.2.0→19.2.8Release Notes
react/react (react)
v19.2.8Compare Source
v19.2.7Compare Source
React Server Components
FormDataentries in Server Actions which regressed in 19.2.6 (@unstubbable#36566)v19.2.6Compare Source
React Server Components
v19.2.5Compare Source
React Server Components
v19.2.4Compare Source
React Server Components
v19.2.3Compare Source
React Server Components
v19.2.2Compare Source
React Server Components
react-server-dom-webpack/*.unbundledto privatereact-server-dom-unbundled(@eps1lon#35290)v19.2.1Compare Source
React Server Components
react/react (react-dom)
v19.2.8Compare Source
v19.2.7Compare Source
React Server Components
FormDataentries in Server Actions which regressed in 19.2.6 (@unstubbable#36566)v19.2.6Compare Source
React Server Components
v19.2.5Compare Source
React Server Components
v19.2.4Compare Source
React Server Components
v19.2.3Compare Source
React Server Components
v19.2.2Compare Source
React Server Components
react-server-dom-webpack/*.unbundledto privatereact-server-dom-unbundled(@eps1lon#35290)v19.2.1Compare Source
React Server Components
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.