[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@vitejs/plugin-react (source)	^5.2.0 → ^6.1.2

---

Release Notes

vitejs/vite-plugin-react (@​vitejs/plugin-react)

v6.1.2

Compare Source

Fix HMR for compound components (#​1484)

Adding or removing a component from a compound component was not handled, creating stale updates. Doing this now triggers hmr invalidate on the file and propagates the invalidation to importers.

Fix compiler.logDiagnostics option not working (#​1483)

With oxc-transform-react >= 0.148, the logDiagnostics was not working. This version fixes it and requires oxc-transform-react >= 0.152 as a peer dependency if you are using the compiler option. compiler.logDiagnostics option is now deprecated and should be swapped for the builtin compiler.reportDiagnostics.

Disable refresh for non-jsx with compiler enabled (fix #​1478) (#​1485)

When the compiler was enabled, TS files could trigger fast refresh which would cause runtime errors. The logic now follows what the builtin oxc plugin in Vite does.

v6.1.1

Compare Source

Add compiler.logDiagnostics option

Recoverable React Compiler diagnostics are no longer logged by default. Set compiler.logDiagnostics to true to log them through Vite. Fatal diagnostics are always logged and fail the transform.

Respect environment sourcemap option for React Compiler transform when builder.sharedPlugins is enabled (#​1439)

The React Compiler transform was using the top-level sourcemap option instead of the environment sourcemap option. This caused a problem when the experimental builder.sharedPlugins was enabled.

v6.1.0

Compare Source

Add experimental native React Compiler support (#​1419)

Add experimental native React Compiler support.

You can use it by installing oxc-transform-react and enabling it via the compiler option:

npm install -D oxc-transform-react

import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'

export default defineConfig({
  plugins: [
     react({ compiler: true })
  ]
})

v6.0.5

Compare Source

Fixed the react compiler preset filter to be linear (#​1353)

The improved filter in v6.0.3 was non-linear and caused a performance regression (#​1349). The filter was changed to be linear to avoid that.

v6.0.4

Compare Source

Fixed $RefreshSig$ is not defined error when running vite dev with NODE_ENV=production

When running vite dev with NODE_ENV=production, the app errored with $RefreshSig$ is not defined.
This error is now fixed.

v6.0.3

Compare Source

Improve the react compiler preset filter to reduce false-positives (#​1138)

Improved the filter in the react compiler babel preset to reduce the false-positives so that less modules are processed by the react compiler.

v6.0.2

Compare Source

Allow all options in reactCompilerPreset (#​1189)

This is a type only change. Only compilationMode and target options were available for reactCompilerPreset.

v6.0.1

Compare Source

Expand @rolldown/plugin-babel peer dep range (#​1146)

Expanded @rolldown/plugin-babel peer dep range to include ^0.2.0.

v6.0.0

Compare Source

---

Configuration

📅 Schedule: (in timezone Europe/London)

• Branch creation
  • Between 12:00 AM and 06:59 AM, only on Monday (* 0-6 * * 1)
• Automerge
  • At any time (no schedule defined)

🚦 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 this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 690ef217-9029-45ae-9d91-0f3fb9e7865f

---

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

🔦 Lighthouse CI

URL	Performance	Accessibility	Best Practices	SEO
http://127.0.0.1:4173/	🟠 76	🟢 100	🟢 100	🟢 100

This repo’s lighthouserc assertions can fail this check.

[rishitank]

Self-review by Claude

Checked package.json and bun.lock.

• The manifest and lockfile agree: plugin-react 6.1.2 is locked, the Babel transitive dependencies it no longer needs are dropped, and @rolldown/pluginutils 1.0.1 is hoisted.
• v6 requires vite ^8, and the repo pins vite 8.1.5, so the peer dependency is satisfied.
• Lint/typecheck/test/build and Browser tests are green.
• The Lighthouse failure is the same one on every open PR in this repo. It does not come from this bump and is being handled in preview-proof #11.

Nothing to fix. This can merge once Lighthouse is green.

[github-actions]

🧪 Runtime gate

✅ Runtime crawl: no runtime errors

1 page(s) opened in a real browser (desktop + phone), safe controls exercised, forms tried with dummy data, links followed client-side, missing-route probe run. 17s.

Coverage: 1/1 routes · 2/3 controls operated · 1/1 forms submitted · 39.1% of the app's own JavaScript executed

Against the default branch: routes ±0, controls −1, JS +0.1 pts.

No visual changes against the last default-branch run.

Pages visited

Page	Status	ms	Controls operated	Forms submitted	Problems
/	200	5688	2/3	1/1	0

⏭️ AI explorer skipped

No GEMINI_API_KEY secret is available to this run, so the Gemini explorer did not run. The deterministic crawl above still gates the change.

Screenshots, diffs and the app log: runtime-gate artifact.

[rishitank]

Independent Claude review (cloud session)

Head reviewed: 9edc39215e34d6ee5991236c8720a41d1c298956 (renovate/vitejs-plugin-react-6.x, 1 commit, based on current main 7e5977f). This supersedes the earlier self-review, which was on 5a2e2e7.

Recommendation: MERGE (low risk). Merging is the owner's call; I have not approved or merged anything.

What changed

@vitejs/plugin-react ^5.2.0 → ^6.1.2. In bun.lock:

• v6 depends only on @rolldown/pluginutils ^1.0.1. Its Babel-based dependencies (@babel/plugin-transform-react-jsx-self/source, @babel/helper-plugin-utils, @types/babel__*, react-refresh) are dropped.
• semver 7.8.5 is hoisted, and semver 6.3.1 is now nested under @babel/core and @babel/helper-compilation-targets. This is a normal re-hoist.
• v6 peer deps are vite ^8 (satisfied by the repo's vite 8.3.3) plus optional @rolldown/plugin-babel, babel-plugin-react-compiler and oxc-transform-react. None are used here.

Release notes (6.0.0 to 6.1.2)

v6 moves the plugin from Babel to Oxc/Rolldown. The 6.0.0 changelog entry is empty, so I checked the peer-dependency and dependency changes in the lockfile instead. The 6.0.x to 6.1.2 notes are fixes and the new opt-in React Compiler (compiler option). None of them affect this repo, which sets no plugin options.

How the plugin is used

vite.config.ts does not import the plugin. @lovable.dev/vite-tanstack-config pulls it in as a peer dependency (>=4.0.0) and wires viteReact itself, so the root devDependency controls which version it gets. I confirmed a single copy, 6.1.2, in node_modules.

Verification (fresh checkout of the head, bun install --frozen-lockfile)

Step	Result
lint	pass (0 errors, 8 warnings, the same 8 as on main)
typecheck	pass
test	pass (8 files, 264 tests)
build	pass (client and SSR/nitro)
dev server (vite dev --host 127.0.0.1)	starts on Vite 8.3.3, / returns 200, and the served button.tsx contains the Fast Refresh transform ($RefreshReg$/$RefreshSig$)
merged together with #12	no conflicts; with #12 merged onto main, lint, typecheck, test and build also pass

Local runs used Node v22.22.0 and Bun 1.4.2; CI pins Bun 1.3.13. I did not exercise HMR in a live browser (the Runtime gate and Browser tests in CI cover the rendered app). The dev server needed --host 127.0.0.1 here only because the sandbox has no IPv6.

Findings (ranked)

1. Info: the dev server logs a Vite notice that vite-tsconfig-paths can be replaced by resolve.tsconfigPaths. This is unrelated to this PR (the plugin comes from the Lovable config) and not actionable here.
2. Info: Runtime gate shows "controls −1" against the default branch (2/3 operated, same as chore(deps): update dependency @types/node to v26 #12's baseline). There are no runtime problems and no visual changes. It looks like crawl variance, but it is worth knowing about.
3. No blocking or medium findings.

Fixes

None needed, so no commits were pushed to this branch.

Gate status

• CI on this head: green. Lint/typecheck/test/build, Browser tests, Lighthouse CI, Runtime gate, Vulnerable dependencies and Secrets all pass. security / Ecosystem audit and flows are skipped, as in the workflow config.
• CodeRabbit: skipped. It posted "Review skipped: Bot user detected" on this PR. I did not trigger it, per instructions. Whether that satisfies "checked on the head" is the owner's call.
• Unresolved threads: none (0 review threads).
• Caveat: Renovate may recreate this branch, which would change the head SHA and make this review stale.

---

Generated by Claude Code