Skip to content

Bump @vitejs/plugin-react from 5.1.2 to 6.1.0 - #49

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/vitejs/plugin-react-6.1.0
Closed

Bump @vitejs/plugin-react from 5.1.2 to 6.1.0#49
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/vitejs/plugin-react-6.1.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 28, 2026

Copy link
Copy Markdown
Contributor

Bumps @vitejs/plugin-react from 5.1.2 to 6.1.0.

Release notes

Sourced from @​vitejs/plugin-react's releases.

plugin-react@6.1.0

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 })
]
})

plugin-react@6.0.5

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.

plugin-react@6.0.4

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.

plugin-react@6.0.3

No release notes provided.

plugin-react@6.0.2

Allow all options in reactCompilerPreset (#1189)

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

plugin-react@6.0.1

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

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

plugin-react@6.0.0

Remove Babel Related Features (#1123)

Vite 8+ can handle React Refresh Transform by Oxc and doesn't need Babel for it. With that, there are no transform applied that requires Babel. To reduce the installation size of this plugin, babel is no longer a dependency of this plugin and the related features are removed.

If you are using Babel, you can use @rolldown/plugin-babel together with this plugin:

... (truncated)

Changelog

Sourced from @​vitejs/plugin-react's changelog.

6.1.0 (2026-08-19)

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 })
]
})

6.0.5 (2026-07-30)

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.

6.0.4 (2026-07-22)

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.

6.0.3 (2026-06-23)

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.

6.0.2 (2026-05-14)

Allow all options in reactCompilerPreset (#1189)

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

6.0.1 (2026-03-13)

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

... (truncated)

Commits
  • 39b3173 release: plugin-react@6.1.0 (#1428)
  • f1340b0 feat(react): add native React Compiler support (#1419)
  • 9ab698e fix(deps): update all non-major dependencies (#1375)
  • 68c0cb8 release: plugin-react@6.0.5 (#1362)
  • 555cdbc fix(react): make the react compiler preset filter linear (#1353)
  • a00a9f8 fix(deps): update all non-major dependencies (#1327)
  • f4b5498 release: plugin-react@6.0.4
  • 7a40659 fix(react): $RefreshSig$ is not defined with NODE_ENV=production vite dev ...
  • 98b32d4 fix(deps): update react 19.2.8 (#1298)
  • 8ae5449 fix: babel-plugin-react-compiler cannot be imported when used in a framework ...
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Aug 28, 2026
Bumps [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/tree/HEAD/packages/plugin-react) from 5.1.2 to 6.1.0.
- [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.1.0/packages/plugin-react)

---
updated-dependencies:
- dependency-name: "@vitejs/plugin-react"
  dependency-version: 6.1.0
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/vitejs/plugin-react-6.1.0 branch from 260cdb4 to 602e72e Compare August 31, 2026 06:15

Copy link
Copy Markdown
Contributor

Not merging — this PR and #50 (vite 7 → 8) are a mutually-blocking pair, and both are gated by electron-vite.

This PR alone fails npm ci:

$ npm ci
npm error Found: vite@7.3.5
npm error Could not resolve dependency:
npm error peer vite@"^8.0.0" from @vitejs/plugin-react@6.1.0

@vitejs/plugin-react@6 requires vite ^8, but vite here is 7.3.5 — and #50, which would raise it, fails on the mirror-image conflict against @vitejs/plugin-react@5.1.2. That is why both ci checks are red: npm ci is CI's first step and dies in ~14s.

Pairing them still does not resolve. The hard cap is in this PR's own trace:

npm error   peer vite@"^5.0.0 || ^6.0.0 || ^7.0.0" from electron-vite@5.0.0

electron-vite@5.0.0 is the latest stable and does not accept vite 8; support lands in electron-vite@6.0.0-beta.0 (peer ^6 || ^7 || ^8), still a beta.

Consequence: electron-vite 6 (stable), vite 8 and @vitejs/plugin-react 6 all have to move together in one PR. Full reasoning and registry evidence in #50 — keeping the detail there so there is one thread to follow.


Generated by Claude Code

BernardJen added a commit that referenced this pull request Sep 3, 2026
#64)

`npm run lint` has never worked (#63). The script existed from the start but
no config ever did, so eslint exited non-zero on every invocation, and nothing
caught it because no workflow ran it.

Fixing that also unblocks #51. Dependabot's eslint 9 -> 10 bump was failing at
`npm ci` with ERESOLVE, not at any check step: eslint-plugin-react@7.37.5 peers
`eslint ^3 || ... || ^9.7` and has no release that accepts 10 (the `next` tag is
a stale 7.8.0-rc.0 peering ^3 || ^4). The plugin was also dead weight - with no
config, nothing had ever referenced it. Dropping it and moving
@typescript-eslint to ^8.69.0, the first line peering `^8.57 || ^9 || ^10`,
leaves nothing in the tree capping eslint's major.

The new config is deliberately not built on @eslint/js, which peers a single
eslint major and would recreate this exact failure on the next bump.

Getting to a clean run needed some dead code removed: unused imports, two catch
bindings that were never read, and `currentPresentationPath` in both Windows
backends, which was written twice and read never (macos.ts genuinely reads it
as a fallback, so it stays there). `require-atomic-updates` is set to 'warn'
rather than disabled - it flags seven pre-existing interleaving hazards in the
automation backends that need a real PowerPoint install to fix safely.

CI runs lint now, between install and typecheck. A lint script no job runs is
how this went unnoticed for the life of the repo.

Finally, dependabot grouping, because #51 was one of four PRs failing the same
way: a solo bump of a package whose peers are pinned to a sibling's major can
never resolve alone. #49 and #50 are the clearest case - one bumps vite to 8,
the other bumps @vitejs/plugin-react to a version requiring vite 8, and each
fails precisely because the other is a separate PR.

Two of the four remain blocked upstream and are not addressed here: #47
(typescript 7) waits on @typescript-eslint, which still peers `<6.1.0`, and
#49/#50 wait on electron-vite 6 leaving beta, since 5.0.0 peers `vite ^5 ||
^6 || ^7`. Grouped, those now sit still instead of failing every week.

Refs #63, #51

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
@dependabot @github

dependabot Bot commented on behalf of github Sep 3, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #66.

@dependabot dependabot Bot closed this Sep 3, 2026
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/vitejs/plugin-react-6.1.0 branch September 3, 2026 19:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant