Update dependency @vitejs/plugin-react to v4

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@vitejs/plugin-react (source)	^2.1.0 -> ^4.1.0

---

Release Notes

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

v4.1.0

Compare Source

• Add @types/babel__cores to dependencies (fix #​211)
• Improve build perf when not using Babel plugins by lazy loading @babel/core #​212
• Better invalidation message when an export is added & fix HMR for export of nullish values #​215
• Include non-dev jsx runtime in optimizeDeps & support HMR for JS files using the non dev runtime #​224
• The build output now contains a index.d.cts file so you don't get types errors when setting moduleResolution to node16 or nodenext in your tsconfig (we recommend using bundler which is more close to how Vite works)

v4.0.4

Compare Source

• Fix #​198: Enable Babel if presets list is not empty

v4.0.3

Compare Source

• Revert #​108: Remove throw when refresh runtime is loaded twice to enable usage in micro frontend apps. This was added to help fix setup usage, and this is not worth an annoying warning for others or a config parameter.

v4.0.2

Compare Source

• Fix fast-refresh for files that are transformed into jsx (#​188)

v4.0.1

Compare Source

• Support Vitest deps.experimentalOptimizer
• Support using components inside web workers (#​181)

v4.0.0

Compare Source

This major version include a revamp of options:

• include/exclude now allow to completely override the files processed by the plugin (#​122). This is more in line with other Rollup/Vite plugins and simplify the setup of enabling Fast Refresh for .mdx files. This can be done like this:

export default defineConfig({
  plugins: [
    { enforce: 'pre', ...mdx() },
    react({ include: /\.(mdx|js|jsx|ts|tsx)$/ }),
  ],
})

These changes also allow to apply Babel plugins on files outside Vite root (expect in node_modules), which improve support for monorepo (fix #​16).

With these changes, only the file extensions is used for filtering processed files and the query param fallback is removed.

• fastRefresh is removed (#​122). This should be correctly activated by plugin without configuration.
• jsxPure is removed. This is a niche use case that was just passing down the boolean to esbuild.jsxSideEffects. (#​129)

The support for React auto import whe using classic runtime is removed. This was prone to errors and added complexity for no good reason given the very wide support of automatic runtime nowadays. This migration path should be as simple as removing the runtime option from the config.

This release goes in hand with the upcoming Vite 4.3 release focusing on performances:

• Cache plugin load (#​141)
• Wrap dynamic import to speedup analysis (#​143)

Other notable changes:

• Silence "use client" warning (#​144, fix #​137)
• Fast Refresh is applied on JS files using automatic runtime (#​122, fix #​83)
• Vite 4.2 is required as a peer dependency (#​128)
• Avoid key collision in React refresh registration (a74dfef, fix #​116)
• Throw when refresh runtime is loaded twice (#​108, fix #​101)
• Don't force optimization of jsx-runtime (#​132)

v3.1.0

Compare Source

• doc: add jsxImportSource option (38d71f6)
• chore: bump release-scripts, typecheck package in CI, remove cache for eslint (9af763d)
• fix: fast-refresh explain link (#​97) (6097795), closes #​97

v3.0.1

Compare Source

• fix: don't invalidate when code is invalid (#​67) (9231a86), closes #​67
• fix(deps): update all non-major dependencies (#​69) (0a8e099), closes #​69

v3.0.0

Compare Source

• chore: update vite to ^4.0.0 (#​57) (941b20d), closes #​57
• chore(deps): update rollup (#​56) (af25ec7), closes #​56
• chore!: drop ast check for refresh boundary (#​43) (e43bd76), closes #​43

v2.2.0

Compare Source

• fix(deps): update all non-major dependencies (#​10610) (bb95467), closes #​10610
• fix(plugin-react): update package.json (#​10479) (7f45eb5), closes #​10479
• chore(deps): update all non-major dependencies (#​10393) (f519423), closes #​10393

---

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: 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. View repository job log here.

[renovate]

⚠ 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: test/casestudies/vite-react-ts-coverable-app/package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: vite-xyz-app@0.0.0
npm ERR! Found: vite@3.2.7
npm ERR! node_modules/vite
npm ERR!   dev vite@"^3.1.8" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer vite@"^4.2.0" from @vitejs/plugin-react@4.1.0
npm ERR! node_modules/@vitejs/plugin-react
npm ERR!   dev @vitejs/plugin-react@"^4.1.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/fbb78c/585e7d/cache/others/npm/_logs/2023-09-24T22_11_09_184Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/fbb78c/585e7d/cache/others/npm/_logs/2023-09-24T22_11_09_184Z-debug-0.log

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 4.x releases. But if you manually upgrade to 4.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.