chore(deps-dev): bump @vitejs/plugin-react from 5.2.0 to 6.0.2#58
chore(deps-dev): bump @vitejs/plugin-react from 5.2.0 to 6.0.2#58dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/tree/HEAD/packages/plugin-react) from 5.2.0 to 6.0.2. - [Release notes](https://github.com/vitejs/vite-plugin-react/releases) - [Changelog](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite-plugin-react/commits/plugin-react@6.0.2/packages/plugin-react) --- updated-dependencies: - dependency-name: "@vitejs/plugin-react" dependency-version: 6.0.2 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
📝 WalkthroughWalkthroughThe ChangesVite React Plugin Dependency Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@package.json`:
- Line 97: The package.json currently specifies "engines.node" as >=20.0.0 which
is too permissive for the dependency `@vitejs/plugin-react` (plugin name:
`@vitejs/plugin-react`, version referenced: ^6.0.2) that requires node: ^20.19.0
|| >=22.12.0; update package.json's engines.node to match that range (e.g.,
">=20.19.0 || >=22.12.0" or the equivalent consolidated semver range) so CI and
developer environments meet the plugin's Node requirement; modify the
engines.node field in package.json accordingly and run install/lockfile
regeneration to ensure consistency with pnpm-lock.yaml.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: c1e8d81e-0bba-40da-85a0-9cb3018c007a
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (1)
package.json
| "@types/gradient-string": "^1.1.6", | ||
| "@types/node": "^22.15.21", | ||
| "@vitejs/plugin-react": "^5.2.0", | ||
| "@vitejs/plugin-react": "^6.0.2", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "== package engines.node =="
node_engine=$(jq -r '.engines.node' package.json)
echo "$node_engine"
echo "== plugin-react resolved version and engines from lockfile =="
awk '
/@vitejs\/plugin-react@6\.0\.2:/, /peerDependenciesMeta:/ { print }
' pnpm-lock.yaml
echo "== direct usage of `@vitejs/plugin-react` in config =="
rg -n -C2 "from '`@vitejs/plugin-react`'|plugins:\s*\[react\(\)\]" vitest.config.tsRepository: forbiddenlink/specter
Length of output: 443
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "== package.json engines.node =="
jq -r '.engines.node' package.json
echo "== package.json engines block (context) =="
jq '.engines' package.json
echo "== package.json pnpm overrides (context) =="
jq '.pnpm // empty | (.overrides // empty)' package.json
echo "== pnpm-lock.yaml: locate `@vitejs/plugin-react` 6.0.2 entry =="
rg -n "`@vitejs/plugin-react`@6\\.0\\.2" pnpm-lock.yaml
rg -n "plugin-react\\`@6`\\.0\\.2" pnpm-lock.yaml
echo "== pnpm-lock.yaml: print around the found entry (small context) =="
python3 - <<'PY'
import re
path="pnpm-lock.yaml"
pat=re.compile(r'`@vitejs/plugin-react`@6\.0\.2')
lines=open(path,'r',encoding='utf-8').read().splitlines()
for i,l in enumerate(lines):
if pat.search(l):
start=max(0,i-15); end=min(len(lines), i+80)
print("\n--- match at line", i+1, "---")
for j in range(start,end):
print(f"{j+1}:{lines[j]}")
PY
echo "== package.json also contains `@vitejs/plugin-react` version spec =="
jq -r '.devDependencies["`@vitejs/plugin-react`"] // .dependencies["`@vitejs/plugin-react`"] // empty' package.jsonRepository: forbiddenlink/specter
Length of output: 1233
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "== package.json devDependencies entry (plugin-react version spec) =="
jq -r '.devDependencies["`@vitejs/plugin-react`"] // .dependencies["`@vitejs/plugin-react`"] // empty' package.json
echo "== package.json engines.node =="
jq -r '.engines.node // empty' package.json
echo "== pnpm-lock.yaml excerpt around line 1344 (base `@vitejs/plugin-react`@6.0.2 entry) =="
sed -n '1335,1375p' pnpm-lock.yaml
echo "== pnpm-lock.yaml excerpt around line 4700 (plugin-react@6.0.2 with vite peer) =="
sed -n '4685,4725p' pnpm-lock.yaml
echo "== locate vitest.config.ts plugin-react import/usage (context) =="
rg -n "from '`@vitejs/plugin-react`'|plugins:\s*\[react\(\)\]" vitest.config.tsRepository: forbiddenlink/specter
Length of output: 3665
Tighten engines.node to match @vitejs/plugin-react’s Node requirement
package.json declares engines.node as >=20.0.0, but pnpm-lock.yaml shows @vitejs/plugin-react@6.0.2 requires engines: { node: ^20.19.0 || >=22.12.0 } (and it’s used in vitest.config.ts via plugins: [react()]). Tighten engines.node to the plugin’s Node range to avoid CI/dev breakage on Node 20.0–20.18.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@package.json` at line 97, The package.json currently specifies "engines.node"
as >=20.0.0 which is too permissive for the dependency `@vitejs/plugin-react`
(plugin name: `@vitejs/plugin-react`, version referenced: ^6.0.2) that requires
node: ^20.19.0 || >=22.12.0; update package.json's engines.node to match that
range (e.g., ">=20.19.0 || >=22.12.0" or the equivalent consolidated semver
range) so CI and developer environments meet the plugin's Node requirement;
modify the engines.node field in package.json accordingly and run
install/lockfile regeneration to ensure consistency with pnpm-lock.yaml.
👻 Specter Analysis
Generated by Specter - Give your codebase a voice |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Bumps @vitejs/plugin-react from 5.2.0 to 6.0.2.
Release notes
Sourced from @vitejs/plugin-react's releases.
... (truncated)
Changelog
Sourced from @vitejs/plugin-react's changelog.
... (truncated)
Commits
6535b55release: plugin-react@6.0.2bf0e43bfeat(react): whitelist debugging-options (#1189)3bd1f08feat: use carets for rolldown versions (#1216)2b8df67fix(deps): update all non-major dependencies (#1218)8fa9619fix(deps): update react 19.2.6 (#1211)a4296adfix(deps): update all non-major dependencies (#1209)323ccd7fix(deps): update all non-major dependencies (#1196)a7506e1chore(deps): update vite 8.0.10 (#1198)02cff2afix(deps): update all non-major dependencies (#1184)4b9c890fix(deps): update react 19.2.5 (#1181)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Summary by CodeRabbit