chore(deps-dev): bump @types/react from 18.3.28 to 19.2.14#72
chore(deps-dev): bump @types/react from 18.3.28 to 19.2.14#72dependabot[bot] wants to merge 1 commit into
Conversation
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
WalkthroughThe ChangesReact Types Dependency Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@package.json`:
- Around line 124-125: The package major versions are misaligned: `@types/react`
is bumped to 19 while the runtime React/ReactDOM and `@types/react-dom` remain on
18, which violates the peer dependency; change the "@types/react" entry back to
an 18.x-compatible version (e.g., ^18.0.0 or matching `@types/react-dom`'s peer
range) so both "@types/react" and "@types/react-dom" share React 18 majors, then
update the lockfile and run your package manager install to ensure dependencies
are consistent; alternatively, if you intend to upgrade runtime, update React
and ReactDOM and both `@types` packages together in the same PR.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| "@types/react": "^19.2.14", | ||
| "@types/react-dom": "^18.3.7", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "== Local package.json versions =="
jq -r '
.dependencies.react as $r |
.dependencies["react-dom"] as $rd |
.devDependencies["@types/react"] as $tr |
.devDependencies["@types/react-dom"] as $trd |
"react=\($r)\nreact-dom=\($rd)\n@types/react=\($tr)\n@types/react-dom=\($trd)"
' package.json
echo
echo "== Remote peerDependencies for `@types/react-dom`@18.3.7 =="
curl -fsSL https://registry.npmjs.org/@types%2freact-dom/18.3.7 | jq '.peerDependencies'
echo
echo "Expected: `@types/react-dom` 18.x should peer with `@types/react` 18.x; if so, current 19.x is mismatched."Repository: adm01-debug/zapp-web
Length of output: 372
Align React type package majors with the installed React runtime
Line 124 upgrades to React 19 types while the project is still on React 18 runtime (Lines 97, 99) and @types/react-dom 18 (Line 125). The registry shows @types/react-dom@18.3.7 requires @types/react@^18.0.0 as a peer dependency—installing @types/react@^19.2.14 violates this constraint and will cause type incompatibilities. Keep React type packages on 18.x until runtime is upgraded, or upgrade React/ReactDOM and both type packages together in one coordinated PR.
Suggested minimal fix (keep runtime on React 18)
- "@types/react": "^19.2.14",
+ "@types/react": "^18.3.28",
"@types/react-dom": "^18.3.7",📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "@types/react": "^19.2.14", | |
| "@types/react-dom": "^18.3.7", | |
| "@types/react": "^18.3.28", | |
| "@types/react-dom": "^18.3.7", |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@package.json` around lines 124 - 125, The package major versions are
misaligned: `@types/react` is bumped to 19 while the runtime React/ReactDOM and
`@types/react-dom` remain on 18, which violates the peer dependency; change the
"@types/react" entry back to an 18.x-compatible version (e.g., ^18.0.0 or
matching `@types/react-dom`'s peer range) so both "@types/react" and
"@types/react-dom" share React 18 majors, then update the lockfile and run your
package manager install to ensure dependencies are consistent; alternatively, if
you intend to upgrade runtime, update React and ReactDOM and both `@types`
packages together in the same PR.
4e63367 to
70d3ead
Compare
70d3ead to
ebcd30d
Compare
Bumps [@types/react](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react) from 18.3.28 to 19.2.14. - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react) --- updated-dependencies: - dependency-name: "@types/react" dependency-version: 19.2.14 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
ebcd30d to
2b5152c
Compare
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🔴 Fechado — base do PR é pré-Onda 1 (regressão massiva)Análise técnica realizada em 2026-05-09: Problema: Este PR foi criado pelo Dependabot em 2026-05-04, baseado num commit ancestral da era Lovable (pré-faxina). Desde então, o repo passou por:
Diff mensurado: mergear este PR aplicaria +6092 files / -5261 deletions em main, revertendo todas as Ondas acima. Plano FX-DEP-02 (pós-deploy):
Referência: |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Bumps @types/react from 18.3.28 to 19.2.14.
Commits