Skip to content
This repository was archived by the owner on Apr 15, 2026. It is now read-only.

chore(deps): update dependency @vitejs/plugin-react to v4.7.0 - #125

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/vitejs-plugin-react-4.x-lockfile
Open

chore(deps): update dependency @vitejs/plugin-react to v4.7.0#125
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/vitejs-plugin-react-4.x-lockfile

Conversation

@renovate

@renovaterenovateBot commented Nov 24, 2024

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

PackageChangeAgeConfidence
@vitejs/plugin-react (source)4.2.14.7.0ageconfidence

Release Notes

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

v4.7.0

Compare Source

Add HMR support for compound components (#​518)

HMR now works for compound components like this:

constRoot=()=><div>Accordion Root</div>constItem=()=><div>Accordion Item</div>exportconstAccordion={ Root, Item }
Return Plugin[] instead of PluginOption[] (#​537)

The return type has changed from react(): PluginOption[] to more specialized type react(): Plugin[]. This allows for type-safe manipulation of plugins, for example:

// previously this causes type errorsreact({babel: {plugins: ['babel-plugin-react-compiler']}}).map(p=>({ ...p,applyToEnvironment: e=>e.name==='client'}))

v4.6.0

Compare Source

Add raw Rolldown support

This plugin only worked with Vite. But now it can also be used with raw Rolldown. The main purpose for using this plugin with Rolldown is to use react compiler.

v4.5.2

Compare Source

Suggest @vitejs/plugin-react-oxc if rolldown-vite is detected #​491

Emit a log which recommends @vitejs/plugin-react-oxc when rolldown-vite is detected to improve performance and use Oxc under the hood. The warning can be disabled by setting disableOxcRecommendation: true in the plugin options.

Use optimizeDeps.rollupOptions instead of optimizeDeps.esbuildOptions for rolldown-vite #​489

This suppresses the warning about optimizeDeps.esbuildOptions being deprecated in rolldown-vite.

Add Vite 7-beta to peerDependencies range #​497

React plugins are compatible with Vite 7, this removes the warning when testing the beta.

v4.5.1

Compare Source

Add explicit semicolon in preambleCode #​485

This fixes an edge case when using HTML minifiers that strips line breaks aggressively.

v4.5.0

Compare Source

Add filter for rolldown-vite #​470

Added filter so that it is more performant when running this plugin with rolldown-powered version of Vite.

Skip HMR for JSX files with hooks #​480

This removes the HMR warning for hooks with JSX.

v4.4.1

Compare Source

Fix type issue when using moduleResolution: "node" in tsconfig #​462

v4.4.0

Compare Source

Make compatible with rolldown-vite

This plugin is now compatible with rolldown-powered version of Vite.
Note that currently the __source property value position might be incorrect. This will be fixed in the near future.

v4.3.4

Compare Source

Add Vite 6 to peerDependencies range

Vite 6 is highly backward compatible, not much to add!

Force Babel to output spec compliant import attributes #​386

The default was an old spec (with type: "json"). We now enforce spec compliant (with { type: "json" })

v4.3.3

Compare Source

React Compiler runtimeModule option removed

React Compiler was updated to accept a target option and runtimeModule was removed. vite-plugin-react will still detect runtimeModule for backwards compatibility.

When using a custom runtimeModule or target !== '19', the plugin will not try to pre-optimize react/compiler-runtime dependency.

The react-compiler-runtime is now available on npm can be used instead of the local shim for people using the compiler with React < 19.

Here is the configuration to use the compiler with React 18 and correct source maps in development:

npm install babel-plugin-react-compiler react-compiler-runtime @&#8203;babel/plugin-transform-react-jsx-development
exportdefaultdefineConfig(({ command })=>{constbabelPlugins=[['babel-plugin-react-compiler',{target: '18'}]]if(command==='serve'){babelPlugins.push(['@&#8203;babel/plugin-transform-react-jsx-development',{}])}return{plugins: [react({babel: {plugins: babelPlugins}})],}})

v4.3.2

Compare Source

Ignore directive sourcemap error #​369

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/37c076bf112a07ba39d0e5f0645fec43

When using a custom runtimeModule, the plugin will not try to pre-optimize react/compiler-runtime dependency.

Reminder: Vite expect code outside of node_modules to be ESM, so you will need to update the gist with import 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:

exportdefaultdefineConfig(({ command })=>{constbabelPlugins=[['babel-plugin-react-compiler',{}]]if(command==='serve'){babelPlugins.push(['@&#8203;babel/plugin-transform-react-jsx-development',{}])}return{plugins: [react({babel: {plugins: babelPlugins}})],}})
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: (UTC)

  • 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 is behind base branch, 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.

@coderabbitai

coderabbitaiBot commented Nov 24, 2024

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

  • 🔍 Trigger a full review

Comment @coderabbitai help to get the list of available commands and usage tips.

@renovate
renovateBotforce-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch 4 times, most recently from 24f7226 to cd0aaaaCompareNovember 24, 2024 18:16
@renovaterenovateBot changed the title chore(deps): update dependency @vitejs/plugin-react to v4.3.3chore(deps): update dependency @vitejs/plugin-react to v4.3.4Nov 26, 2024
@renovate
renovateBotforce-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch 3 times, most recently from 1295bbd to d4ca3feCompareJanuary 30, 2025 17:26
@renovate
renovateBotforce-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch from d4ca3fe to 3e47212CompareFebruary 9, 2025 13:49
@renovate
renovateBotforce-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch from 3e47212 to 03b62ebCompareMarch 3, 2025 12:20
@renovate
renovateBotforce-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch 3 times, most recently from 1165b03 to da1227bCompareMarch 17, 2025 17:49
@renovate
renovateBotforce-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch from da1227b to c7b483fCompareApril 1, 2025 12:25
@renovate
renovateBotforce-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch from c7b483f to 0a622bbCompareApril 15, 2025 12:33
@renovaterenovateBot changed the title chore(deps): update dependency @vitejs/plugin-react to v4.3.4chore(deps): update dependency @vitejs/plugin-react to v4.4.0Apr 15, 2025
@renovaterenovateBot changed the title chore(deps): update dependency @vitejs/plugin-react to v4.4.0chore(deps): update dependency @vitejs/plugin-react to v4.4.1Apr 19, 2025
@renovate
renovateBotforce-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch from 0a622bb to 3a45aa3CompareApril 24, 2025 08:04
@renovate
renovateBotforce-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch 2 times, most recently from 29cb512 to e008cb4CompareMay 23, 2025 01:58
@renovaterenovateBot changed the title chore(deps): update dependency @vitejs/plugin-react to v4.4.1chore(deps): update dependency @vitejs/plugin-react to v4.5.0May 23, 2025
@renovate
renovateBotforce-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch from e008cb4 to 6305156CompareMay 28, 2025 13:59
@renovaterenovateBot changed the title chore(deps): update dependency @vitejs/plugin-react to v4.5.0chore(deps): update dependency @vitejs/plugin-react to v4.5.1Jun 6, 2025
@renovate
renovateBotforce-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch from 6305156 to 4c70778CompareJune 6, 2025 01:40
@renovaterenovateBot changed the title chore(deps): update dependency @vitejs/plugin-react to v4.5.1chore(deps): update dependency @vitejs/plugin-react to v4.5.2Jun 10, 2025
@renovaterenovateBot changed the title chore(deps): update dependency @vitejs/plugin-react to v4.5.2chore(deps): update dependency @vitejs/plugin-react to v4.6.0Jun 23, 2025
@renovate
renovateBotforce-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch from 4c70778 to 2465c0bCompareJuly 2, 2025 18:46
@renovate
renovateBotforce-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch from 2465c0b to 5b9ad4eCompareJuly 18, 2025 07:33
@renovaterenovateBot changed the title chore(deps): update dependency @vitejs/plugin-react to v4.6.0chore(deps): update dependency @vitejs/plugin-react to v4.7.0Jul 18, 2025
@renovate
renovateBotforce-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch 2 times, most recently from 7c2dabb to 38f254cCompareAugust 13, 2025 11:45
@renovate
renovateBotforce-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch from 38f254c to 057d3c4CompareAugust 19, 2025 16:42
@renovate
renovateBotforce-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch from 057d3c4 to ad9e4f3CompareAugust 31, 2025 12:44
@renovate
renovateBotforce-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch from ad9e4f3 to 588f82eCompareSeptember 25, 2025 15:56
@renovate
renovateBotforce-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch from 588f82e to fb8a1ecCompareOctober 21, 2025 10:50
@renovate
renovateBotforce-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch from fb8a1ec to 171621dCompareNovember 19, 2025 23:55
@renovate
renovateBotforce-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch from 171621d to 196f781CompareDecember 3, 2025 19:26
@renovate
renovateBotforce-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch from 196f781 to 61ee990CompareDecember 31, 2025 15:52
@renovate
renovateBotforce-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch from 61ee990 to 3ff0d65CompareJanuary 8, 2026 20:03
@renovate
renovateBotforce-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch 2 times, most recently from 5e8c3d5 to 7c36fd3CompareJanuary 23, 2026 17:10
@renovate
renovateBotforce-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch from 7c36fd3 to 040ac07CompareFebruary 2, 2026 21:55
@renovate
renovateBotforce-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch from 040ac07 to 0583a90CompareFebruary 12, 2026 11:12
@renovate
renovateBotforce-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch from 0583a90 to 34a0ce1CompareFebruary 19, 2026 11:17
@renovate
renovateBotforce-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch 2 times, most recently from 5205cc1 to 77079c4CompareMarch 13, 2026 16:42
@renovate
renovateBotforce-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch from 77079c4 to c8ff5e4CompareApril 1, 2026 18:59
@renovate
renovateBotforce-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch from c8ff5e4 to 73ed54aCompareApril 8, 2026 20:53
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants