Skip to content

chore(deps): update dependency @vitejs/plugin-react to v5.2.0#3158

Open
renovate[bot] wants to merge 1 commit intocanaryfrom
renovate/vitejs-plugin-react-5.x
Open

chore(deps): update dependency @vitejs/plugin-react to v5.2.0#3158
renovate[bot] wants to merge 1 commit intocanaryfrom
renovate/vitejs-plugin-react-5.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Apr 2, 2026

This PR contains the following updates:

Package Change Age Confidence
@vitejs/plugin-react (source) 5.1.45.2.0 age confidence

Release Notes

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

v5.2.0

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Never, 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.


Summary by cubic

Upgrade @vitejs/plugin-react from 5.1.4 to 5.2.0 to stay current with Vite and improve HMR reliability during local development. Supports OSS-5 by aligning the toolchain for hot reloads with TypeScript path aliases.

  • Dependencies
    • Bump @vitejs/plugin-react to 5.2.0 in the workspace catalog and lockfile; peer range now includes vite@^8.

Written for commit 2a2128b. Summary will update on new commits.

@vercel
Copy link
Copy Markdown
Contributor

vercel bot commented Apr 2, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
react-email Ready Ready Preview, Comment Apr 2, 2026 6:44am
react-email-demo Ready Ready Preview, Comment Apr 2, 2026 6:44am
react-email-examples Ready Ready Preview, Comment Apr 2, 2026 6:44am

Request Review

@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Apr 2, 2026

⚠️ No Changeset found

Latest commit: 2a2128b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@socket-security
Copy link
Copy Markdown

@socket-security
Copy link
Copy Markdown

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Block Medium
Install-time scripts: npm esbuild during postinstall

Install script: postinstall

Source: node install.js

From: packages/preview-server/package.jsonnpm/esbuild@0.27.4

ℹ Read more on: This package | This alert | What is an install script?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/esbuild@0.27.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

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

No issues found across 2 files

Confidence score: 5/5

  • Automated review surfaced no issues in the provided summaries.
  • No files require special attention.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants