Update dependency @vitejs/plugin-react to v4.3.1 #15
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/vitejs-plugin-react-4.x-lockfile"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
4.2.1
->4.3.1
Release Notes
vitejs/vite-plugin-react (@vitejs/plugin-react)
v4.3.1
Compare Source
Fix support for React Compiler with React 18
The previous version made this assumption that the compiler was only usable with React 19, but it's possible to use it with React 18 and a custom
runtimeModule
: https://gist.github.com/poteto/37c076bf112a07ba39d0e5f0645fec43When using a custom
runtimeModule
, the plugin will not try to pre-optimizereact/compiler-runtime
dependency.Reminder: Vite expect code outside of
node_modules
to be ESM, so you will need to update the gist withimport React from 'react'
.v4.3.0
Compare Source
Fix support for React compiler
Don't set
retainLines: true
when the React compiler is used. This creates whitespace issues and the compiler is modifying the JSX too much to get correct line numbers after that. If you want to use the React compiler and get back correct line numbers for tools like vite-plugin-react-click-to-component to work, you should update your config to something like:Support HMR for class components
This is a long overdue and should fix some issues people had with HMR when migrating from CRA.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.
This PR has been generated by Renovate Bot.
Update dependency @vitejs/plugin-react to v4.3.0to Update dependency @vitejs/plugin-react to v4.3.1b36bc8b0a8
toe37ba8329a