chore(deps): update dependency @vitejs/plugin-react to v6.0.5 #272

Merged

renovate-bot merged 2 commits from renovate/vitejs-plugin-react-6.x into main 2026-08-07 00:04:22 +00:00

Conversation 2 Commits 2 Files changed 2 +301 -352

renovate-bot commented 2026-08-03 00:07:54 +00:00

Contributor

Copy link

This PR contains the following updates:

Package	Change	Age	Confidence
@vitejs/plugin-react (source)	6.0.3 → 6.0.5

---

Release Notes

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

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.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 9am on monday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 has been generated by Mend Renovate.

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/tree/main/packages/plugin-react#readme) ([source](https://github.com/vitejs/vite-plugin-react/tree/HEAD/packages/plugin-react)) | [`6.0.3` → `6.0.5`](https://renovatebot.com/diffs/npm/@vitejs%2fplugin-react/6.0.3/6.0.5) |  |  | --- ### Release Notes <details> <summary>vitejs/vite-plugin-react (@&#8203;vitejs/plugin-react)</summary> ### [`v6.0.5`](https://github.com/vitejs/vite-plugin-react/blob/HEAD/packages/plugin-react/CHANGELOG.md#605-2026-07-30) [Compare Source](https://github.com/vitejs/vite-plugin-react/compare/f4b549822ec239799d746c030abb0b9a7d8f0a04...68c0cb8796ce18bd049c3d05c5210eaf0617eac0) ##### Fixed the react compiler preset filter to be linear ([#&#8203;1353](https://github.com/vitejs/vite-plugin-react/pull/1353)) The improved filter in v6.0.3 was non-linear and caused a performance regression ([#&#8203;1349](https://github.com/vitejs/vite-plugin-react/issues/1349)). The filter was changed to be linear to avoid that. ### [`v6.0.4`](https://github.com/vitejs/vite-plugin-react/blob/HEAD/packages/plugin-react/CHANGELOG.md#604-2026-07-22) [Compare Source](https://github.com/vitejs/vite-plugin-react/compare/640fd358a0e82393acfce4e92e19a6ac6e1641a7...f4b549822ec239799d746c030abb0b9a7d8f0a04) ##### 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. </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - "before 9am on monday" - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yODAuMyIsInVwZGF0ZWRJblZlciI6IjQzLjI4MC4zIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiXX0=-->

renovate-bot scheduled this pull request to auto merge when all checks succeed 2026-08-03 00:07:56 +00:00

renovate-bot commented 2026-08-03 00:07:57 +00:00

Author

Contributor

Copy link

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: webapp/frontend/package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: quest-board@0.1.0
npm error Found: @babel/core@7.29.7
npm error node_modules/@babel/core
npm error   peer @babel/core@"^7.0.0" from @babel/helper-create-class-features-plugin@7.29.7
npm error   node_modules/@babel/helper-create-class-features-plugin
npm error     @babel/helper-create-class-features-plugin@"^7.29.7" from @babel/plugin-transform-class-properties@7.29.7
npm error     node_modules/@babel/plugin-transform-class-properties
npm error       @babel/plugin-transform-class-properties@"^7.29.7" from @babel/preset-env@7.29.7
npm error       node_modules/@babel/preset-env
npm error         @babel/preset-env@"^7.11.0" from workbox-build@7.4.1
npm error         node_modules/workbox-build
npm error     @babel/helper-create-class-features-plugin@"^7.29.7" from @babel/plugin-transform-class-static-block@7.29.7
npm error     node_modules/@babel/plugin-transform-class-static-block
npm error       @babel/plugin-transform-class-static-block@"^7.29.7" from @babel/preset-env@7.29.7
npm error       node_modules/@babel/preset-env
npm error         @babel/preset-env@"^7.11.0" from workbox-build@7.4.1
npm error         node_modules/workbox-build
npm error     2 more (@babel/plugin-transform-private-methods, @babel/plugin-transform-private-property-in-object)
npm error   peer @babel/core@"^7.0.0" from @babel/helper-create-regexp-features-plugin@7.29.7
npm error   node_modules/@babel/helper-create-regexp-features-plugin
npm error     @babel/helper-create-regexp-features-plugin@"^7.18.6" from @babel/plugin-syntax-unicode-sets-regex@7.18.6
npm error     node_modules/@babel/plugin-syntax-unicode-sets-regex
npm error       @babel/plugin-syntax-unicode-sets-regex@"^7.18.6" from @babel/preset-env@7.29.7
npm error       node_modules/@babel/preset-env
npm error         @babel/preset-env@"^7.11.0" from workbox-build@7.4.1
npm error         node_modules/workbox-build
npm error     @babel/helper-create-regexp-features-plugin@"^7.29.7" from @babel/plugin-transform-dotall-regex@7.29.7
npm error     node_modules/@babel/plugin-transform-dotall-regex
npm error       @babel/plugin-transform-dotall-regex@"^7.29.7" from @babel/preset-env@7.29.7
npm error       node_modules/@babel/preset-env
npm error         @babel/preset-env@"^7.11.0" from workbox-build@7.4.1
npm error         node_modules/workbox-build
npm error     6 more (...)
npm error   73 more (@babel/helper-define-polyfill-provider, ...)
npm error
npm error Could not resolve dependency:
npm error dev @vitejs/plugin-react@"6.0.5" from the root project
npm error
npm error Conflicting peer dependency: @babel/core@8.0.1
npm error node_modules/@babel/core
npm error   peer @babel/core@"^8.0.0" from @babel/plugin-transform-runtime@8.0.1
npm error   node_modules/@babel/plugin-transform-runtime
npm error     peerOptional @babel/plugin-transform-runtime@"^7.29.0 || ^8.0.0-rc.1" from @rolldown/plugin-babel@0.2.3
npm error     node_modules/@rolldown/plugin-babel
npm error       peerOptional @rolldown/plugin-babel@"^0.1.7 || ^0.2.0" from @vitejs/plugin-react@6.0.5
npm error       node_modules/@vitejs/plugin-react
npm error         dev @vitejs/plugin-react@"6.0.5" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2026-08-06T00_10_44_643Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-08-06T00_10_44_643Z-debug-0.log

### ⚠️ Artifact update problem Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens: - any of the package files in this branch needs updating, or - the branch becomes conflicted, or - you click the rebase/retry checkbox if found above, or - you rename this PR's title to start with "rebase!" to trigger it manually The artifact failure details are included below: ##### File name: webapp/frontend/package-lock.json ``` npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options. npm error code ERESOLVE npm error ERESOLVE could not resolve npm error npm error While resolving: quest-board@0.1.0 npm error Found: @babel/core@7.29.7 npm error node_modules/@babel/core npm error peer @babel/core@"^7.0.0" from @babel/helper-create-class-features-plugin@7.29.7 npm error node_modules/@babel/helper-create-class-features-plugin npm error @babel/helper-create-class-features-plugin@"^7.29.7" from @babel/plugin-transform-class-properties@7.29.7 npm error node_modules/@babel/plugin-transform-class-properties npm error @babel/plugin-transform-class-properties@"^7.29.7" from @babel/preset-env@7.29.7 npm error node_modules/@babel/preset-env npm error @babel/preset-env@"^7.11.0" from workbox-build@7.4.1 npm error node_modules/workbox-build npm error @babel/helper-create-class-features-plugin@"^7.29.7" from @babel/plugin-transform-class-static-block@7.29.7 npm error node_modules/@babel/plugin-transform-class-static-block npm error @babel/plugin-transform-class-static-block@"^7.29.7" from @babel/preset-env@7.29.7 npm error node_modules/@babel/preset-env npm error @babel/preset-env@"^7.11.0" from workbox-build@7.4.1 npm error node_modules/workbox-build npm error 2 more (@babel/plugin-transform-private-methods, @babel/plugin-transform-private-property-in-object) npm error peer @babel/core@"^7.0.0" from @babel/helper-create-regexp-features-plugin@7.29.7 npm error node_modules/@babel/helper-create-regexp-features-plugin npm error @babel/helper-create-regexp-features-plugin@"^7.18.6" from @babel/plugin-syntax-unicode-sets-regex@7.18.6 npm error node_modules/@babel/plugin-syntax-unicode-sets-regex npm error @babel/plugin-syntax-unicode-sets-regex@"^7.18.6" from @babel/preset-env@7.29.7 npm error node_modules/@babel/preset-env npm error @babel/preset-env@"^7.11.0" from workbox-build@7.4.1 npm error node_modules/workbox-build npm error @babel/helper-create-regexp-features-plugin@"^7.29.7" from @babel/plugin-transform-dotall-regex@7.29.7 npm error node_modules/@babel/plugin-transform-dotall-regex npm error @babel/plugin-transform-dotall-regex@"^7.29.7" from @babel/preset-env@7.29.7 npm error node_modules/@babel/preset-env npm error @babel/preset-env@"^7.11.0" from workbox-build@7.4.1 npm error node_modules/workbox-build npm error 6 more (...) npm error 73 more (@babel/helper-define-polyfill-provider, ...) npm error npm error Could not resolve dependency: npm error dev @vitejs/plugin-react@"6.0.5" from the root project npm error npm error Conflicting peer dependency: @babel/core@8.0.1 npm error node_modules/@babel/core npm error peer @babel/core@"^8.0.0" from @babel/plugin-transform-runtime@8.0.1 npm error node_modules/@babel/plugin-transform-runtime npm error peerOptional @babel/plugin-transform-runtime@"^7.29.0 || ^8.0.0-rc.1" from @rolldown/plugin-babel@0.2.3 npm error node_modules/@rolldown/plugin-babel npm error peerOptional @rolldown/plugin-babel@"^0.1.7 || ^0.2.0" from @vitejs/plugin-react@6.0.5 npm error node_modules/@vitejs/plugin-react npm error dev @vitejs/plugin-react@"6.0.5" from the root project npm error npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution. npm error npm error npm error For a full report see: npm error /tmp/renovate/cache/others/npm/_logs/2026-08-06T00_10_44_643Z-eresolve-report.txt npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-08-06T00_10_44_643Z-debug-0.log ```

renovate-bot force-pushed renovate/vitejs-plugin-react-6.x from 072d242e2d to caaa2fd962 2026-08-03 06:09:05 +00:00 Compare

renovate-bot force-pushed renovate/vitejs-plugin-react-6.x from caaa2fd962 to ba39972ddf 2026-08-03 12:07:53 +00:00 Compare

renovate-bot force-pushed renovate/vitejs-plugin-react-6.x from ba39972ddf to e9adc7419f 2026-08-06 00:10:59 +00:00 Compare

rbrooks force-pushed renovate/vitejs-plugin-react-6.x from e9adc7419f to aaa1d8588d 2026-08-06 23:59:37 +00:00 Compare

rbrooks referenced this pull request from a commit 2026-08-06 23:59:38 +00:00

chore(deps): regenerate frontend lockfile for @vitejs/plugin-react 6.0.5

claude-bot commented 2026-08-06 23:59:51 +00:00

Contributor

Copy link

Pushed a regenerated package-lock.json and rebased onto current main (the branch predated v3.11.1–v3.11.3).

Why CI failed in 26s: not a test failure. Renovate's own artifact update hit ERESOLVE (see its warning comment above), so this PR was opened with package.json only and no lockfile change — npm ci then died on the package/lock mismatch before a single test ran.

Root cause. The conflict is an artefact of npm's incremental lockfile update, not of 6.0.5. Bumping the plugin makes npm re-walk its optional peer chain:

@vitejs/plugin-react@6.0.5
  └─ peerOptional @rolldown/plugin-babel ^0.1.7 || ^0.2.0   → 0.2.3
       └─ peerOptional @babel/plugin-transform-runtime ^7.29.0 || ^8.0.0-rc.1
            → npm selects the 8.x line → requires @babel/core ^8

That collides with @babel/core@7.29.7, which vite-plugin-pwa → workbox-build → @babel/preset-env@^7 pins and ~75 @babel/* packages peer-depend on.

The key detail: 6.0.3 declares the identical peer range, and neither optional peer is in the lockfile at all. A from-scratch resolve never takes that path — 6.0.3, 6.0.5, and 6.0.5-with-overrides all resolve cleanly. Only the incremental update against the existing lock fails.

Fix: regenerate the lockfile. Neither optional peer is installed, @babel/core stays 7.29.7, and the remaining churn is 59 patch/minor floats already inside existing ranges (@babel/* 7.29.7→7.29.8, rollup 4.62.2→4.62.4, @types/react patch), plus 6 added / 12 removed nested dedupe artifacts.

No overrides guard added — deliberately. I checked whether this recurs: the next real pending update (vite 8.1.5 → 8.2.1) resolves incrementally on both the old and the regenerated lockfile. The conflict is specific to bumping plugin-react itself, since that is the package whose optional-peer chain gets re-walked, so a permanent override would be dead weight.

Verified locally in a node:20-slim container against the regenerated lock — all five CI steps: npm ci (606 packages), eslint (0 errors; 1 pre-existing exhaustive-deps warning, tracked in #21), vitest 431/431 passed, npm run build, and the prod audit gate (Audit clean, allowlist untouched).

Pushed a regenerated `package-lock.json` and rebased onto current `main` (the branch predated v3.11.1–v3.11.3). **Why CI failed in 26s:** not a test failure. Renovate's own artifact update hit `ERESOLVE` (see its warning comment above), so this PR was opened with `package.json` only and no lockfile change — `npm ci` then died on the package/lock mismatch before a single test ran. **Root cause.** The conflict is an artefact of npm's *incremental* lockfile update, not of 6.0.5. Bumping the plugin makes npm re-walk its optional peer chain: ``` @vitejs/plugin-react@6.0.5 └─ peerOptional @rolldown/plugin-babel ^0.1.7 || ^0.2.0 → 0.2.3 └─ peerOptional @babel/plugin-transform-runtime ^7.29.0 || ^8.0.0-rc.1 → npm selects the 8.x line → requires @babel/core ^8 ``` That collides with `@babel/core@7.29.7`, which `vite-plugin-pwa` → `workbox-build` → `@babel/preset-env@^7` pins and ~75 `@babel/*` packages peer-depend on. The key detail: **6.0.3 declares the identical peer range**, and neither optional peer is in the lockfile at all. A from-scratch resolve never takes that path — 6.0.3, 6.0.5, and 6.0.5-with-overrides all resolve cleanly. Only the incremental update against the existing lock fails. **Fix:** regenerate the lockfile. Neither optional peer is installed, `@babel/core` stays 7.29.7, and the remaining churn is 59 patch/minor floats already inside existing ranges (`@babel/* 7.29.7→7.29.8`, `rollup 4.62.2→4.62.4`, `@types/react` patch), plus 6 added / 12 removed nested dedupe artifacts. **No `overrides` guard added** — deliberately. I checked whether this recurs: the next real pending update (`vite 8.1.5 → 8.2.1`) resolves incrementally on both the old and the regenerated lockfile. The conflict is specific to bumping `plugin-react` itself, since that is the package whose optional-peer chain gets re-walked, so a permanent override would be dead weight. Verified locally in a `node:20-slim` container against the regenerated lock — all five CI steps: `npm ci` (606 packages), `eslint` (0 errors; 1 pre-existing `exhaustive-deps` warning, tracked in #21), `vitest` **431/431 passed**, `npm run build`, and the prod audit gate (`Audit clean`, allowlist untouched).

renovate-bot merged commit e6a608d513 into main 2026-08-07 00:04:22 +00:00

renovate-bot deleted branch renovate/vitejs-plugin-react-6.x 2026-08-07 00:04:23 +00:00

renovate-bot referenced this pull request from a commit 2026-08-07 00:04:24 +00:00

Merge pull request 'chore(deps): update dependency @vitejs/plugin-react to v6.0.5' (#272) from renovate/vitejs-plugin-react-6.x into main

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

backend

Issue related to the backend

  

bot

Issue related to the bot

  

bug

Something is not working

  

duplicate

This issue or pull request already exists

  

enhancement

New feature

  

frontend

Issue related to the frontend

  

help wanted

Need some help

  

invalid

Something is wrong

  

question

More information is needed

  

recording

Issue related to the recording system

  

security

Security hardening / vulnerability work

  

wontfix

This won't be fixed

No labels

backend

bot

bug

duplicate

enhancement

frontend

help wanted

invalid

question

recording

security

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

3 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

rbrooks/Quest-Board!272

No description provided.