Skip to content

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

Open
renovate-appwrite[bot] wants to merge 1 commit into
mainfrom
renovate/vitejs-plugin-react-6.x
Open

renovate-appwrite[bot] wants to merge 1 commit into
mainfrom
renovate/vitejs-plugin-react-6.x

Conversation

@renovate-appwrite

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@vitejs/plugin-react (source) ^5.0.4 → ^6.0.0 age confidence

Release Notes

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

v6.3.0

Compare Source

Make reactCompilerPreset work with @rolldown/plugin-babel's parallel option (#​1549)

reactCompilerPreset now refers to its Babel preset by module path instead of by function, so it can be sent to worker threads.

v6.2.1

Compare Source

Fix refreshInclude and refreshExclude options not working (#​1543)

Fix mistake from #​1516

v6.2.0

Compare Source

Add refreshInclude and refreshExclude options (#​1516)

Add refreshInclude and refreshExclude options to skip fast refresh for certain files that won't run in the browser.

Expand oxc-transform-react peer dependency range (#​1540)

The peer dependency version range for oxc-transform-react was expanded from ^0.152.0 to >=0.152.0 <0.157.0.

Expand @rolldown/plugin-babel peer dependency range (#​1541)

The peer dependency version range for @rolldown/plugin-babel was expanded from ^0.1.7 || ^0.2.0 to ^0.1.7 || ^0.2.0 || ^0.3.0.

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

v5.2.0

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Only on Monday (* * * * 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 has been generated by Mend Renovate CLI.

@renovate-appwrite

Copy link
Copy Markdown
Contributor Author

⚠️ 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: 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 unable to resolve dependency tree
npm error
npm error While resolving: appwrite-arena@undefined
npm error Found: vite@7.3.8
npm error node_modules/vite
npm error   dev vite@"^7.3.7" from the root project
npm error
npm error Could not resolve dependency:
npm error peer vite@"^8.0.0" from @vitejs/plugin-react@6.3.0
npm error node_modules/@vitejs/plugin-react
npm error   dev @vitejs/plugin-react@"^6.0.0" 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-11-16T14_52_21_417Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-11-16T14_52_21_417Z-debug-0.log

@appwrite

appwrite Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

🟡 Tier B · Needs changes before merging

The locked plugin/Vite combination makes the build and test commands fail before the app can run.

The dependency declaration upgrades @vitejs/plugin-react from v5 to v6. The pnpm lockfile is refreshed to resolve the new plugin and related dependency versions.

Verdict New comments Fixed Still open
🛑 Changes requested 1 0 0
Finding Where
🟠 plugin-react 6.3.0 requires Vite 8 pnpm-lock.yaml:2326
Fix with agent prompt
### Issue 1
pnpm-lock.yaml:2326
**plugin-react 6.3.0 requires Vite 8**

This lock entry declares `vite: ^8.0.0`, but the app still locks Vite 7.3.7. With this combination, `pnpm build` and `pnpm test` fail loading `vite.config.ts` with `ERR_PACKAGE_PATH_NOT_EXPORTED` for `vite/internal`; please upgrade Vite alongside this plugin or keep plugin-react on v5.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
📂 Walkthrough · 2
File Change
package.json Bumps the declared React Vite plugin version.
pnpm-lock.yaml Locks plugin-react 6.3.0 and refreshes its dependency graph.

Reviewed 8e83cb8 · Details · Comment @appwrite review to re-run, or mention @appwrite with a question.

@appwrite appwrite Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Tier B · 1 blocking finding to address. Summary

Comment thread pnpm-lock.yaml

'@vitejs/plugin-react@5.1.4':
resolution: {integrity: sha512-VIcFLdRi/VYRU8OL/puL7QXMYafHmqOnwTZY50U1JPlCNj30PxCMx65c494b1K9be9hX83KVt0+gTEwTWLqToA==}
'@vitejs/plugin-react@6.3.0':

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

plugin-react 6.3.0 requires Vite 8

This lock entry declares vite: ^8.0.0, but the app still locks Vite 7.3.7. With this combination, pnpm build and pnpm test fail loading vite.config.ts with ERR_PACKAGE_PATH_NOT_EXPORTED for vite/internal; please upgrade Vite alongside this plugin or keep plugin-react on v5.

Prompt To Fix With AI
This is a comment left during a code review.
Path: pnpm-lock.yaml
Line: 2326

Comment:
**plugin-react 6.3.0 requires Vite 8**

This lock entry declares `vite: ^8.0.0`, but the app still locks Vite 7.3.7. With this combination, `pnpm build` and `pnpm test` fail loading `vite.config.ts` with `ERR_PACKAGE_PATH_NOT_EXPORTED` for `vite/internal`; please upgrade Vite alongside this plugin or keep plugin-react on v5.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

🟠 Major · bug · Reply if this doesn't apply.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants