chore(deps): update dependency @vitejs/plugin-react to v4 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@vitejs/plugin-react (source)	^3.1.0 -> ^4.0.0
@vitejs/plugin-react (source)	^1.1.0 -> ^4.0.0

---

Release Notes

vitejs/vite-plugin-react

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)

---

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 these updates 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: cases/perf-1/pnpm-lock.yaml

installing v2 tool node v18.16.0
linking tool node v18.16.0
node: v18.16.0 /usr/local/bin/node
npm: 9.5.1  /usr/local/bin/npm
Installed v2 /usr/local/buildpack/tools/v2/node.sh in 4 seconds
installing v2 tool pnpm v8.3.1
linking tool pnpm v8.3.1
8.3.1
Installed v2 /usr/local/buildpack/tools/v2/pnpm.sh in 1 seconds
Scope: all 2 workspace projects
/mnt/renovate/gh/vitejs/vite-benchmark/cases/perf-2:
 ERR_PNPM_LINKED_PKG_DIR_NOT_FOUND  Could not install from "/mnt/renovate/gh/vitejs/vite-benchmark/cases/vite" as it does not exist.

This error happened while installing a direct dependency of /mnt/renovate/gh/vitejs/vite-benchmark/cases/perf-2