vitejs/vite-plugin-react (@vitejs/plugin-react)
### [`v4.3.1`](https://togithub.com/vitejs/vite-plugin-react/blob/HEAD/packages/plugin-react/CHANGELOG.md#431-2024-06-10)
[Compare Source](https://togithub.com/vitejs/vite-plugin-react/compare/v4.3.0...v4.3.1)
##### 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`](https://togithub.com/vitejs/vite-plugin-react/blob/HEAD/packages/plugin-react/CHANGELOG.md#430-2024-05-22)
[Compare Source](https://togithub.com/vitejs/vite-plugin-react/compare/v4.2.1...v4.3.0)
##### 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](https://togithub.com/ArnaudBarre/vite-plugin-react-click-to-component) to work, you should update your config to something like:
```ts
export default defineConfig(({ command }) => {
const babelPlugins = [['babel-plugin-react-compiler', {}]]
if (command === 'serve') {
babelPlugins.push(['@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.
### [`v4.2.1`](https://togithub.com/vitejs/vite-plugin-react/blob/HEAD/packages/plugin-react/CHANGELOG.md#421-2023-12-04)
[Compare Source](https://togithub.com/vitejs/vite-plugin-react/compare/v4.2.0...v4.2.1)
Remove generic parameter on `Plugin` to avoid type error with Rollup 4/Vite 5 and `skipLibCheck: false`.
I expect very few people to currently use this feature, but if you are extending the React plugin via `api` object, you can get back the typing of the hook by importing `ViteReactPluginApi`:
```ts
import type { Plugin } from 'vite'
import type { ViteReactPluginApi } from '@vitejs/plugin-react'
export const somePlugin: Plugin = {
name: 'some-plugin',
api: {
reactBabel: (babelConfig) => {
babelConfig.plugins.push('some-babel-plugin')
},
} satisfies ViteReactPluginApi,
}
```
### [`v4.2.0`](https://togithub.com/vitejs/vite-plugin-react/blob/HEAD/packages/plugin-react/CHANGELOG.md#420-2023-11-16)
[Compare Source](https://togithub.com/vitejs/vite-plugin-react/compare/v4.1.1...v4.2.0)
##### Update peer dependency range to target Vite 5
There were no breaking change that impacted this plugin, so any combination of React plugins and Vite core version will work.
##### Align jsx runtime for optimized dependencies
This will only affect people using internal libraries that contains untranspiled JSX. This change aligns the optimizer with the source code and avoid issues when the published source don't have `React` in the scope.
Reminder: While being partially supported in Vite, publishing TS & JSX outside of internal libraries is highly discouraged.
### [`v4.1.1`](https://togithub.com/vitejs/vite-plugin-react/blob/HEAD/packages/plugin-react/CHANGELOG.md#411-2023-11-02)
[Compare Source](https://togithub.com/vitejs/vite-plugin-react/compare/v4.1.0...v4.1.1)
- Enable retainLines to get correct line numbers for jsxDev (fix [#235](https://togithub.com/vitejs/vite-plugin-react/issues/235))
### [`v4.1.0`](https://togithub.com/vitejs/vite-plugin-react/blob/HEAD/packages/plugin-react/CHANGELOG.md#410-2023-09-24)
[Compare Source](https://togithub.com/vitejs/vite-plugin-react/compare/v4.0.4...v4.1.0)
- Add `@types/babel__cores` to dependencies (fix [#211](https://togithub.com/vitejs/vite-plugin-react/issues/211))
- Improve build perf when not using Babel plugins by lazy loading `@babel/core` [#212](https://togithub.com/vitejs/vite-plugin-react/pull/212)
- Better invalidation message when an export is added & fix HMR for export of nullish values [#215](https://togithub.com/vitejs/vite-plugin-react/pull/215)
- Include non-dev jsx runtime in optimizeDeps & support HMR for JS files using the non dev runtime [#224](https://togithub.com/vitejs/vite-plugin-react/pull/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`](https://togithub.com/vitejs/vite-plugin-react/blob/HEAD/packages/plugin-react/CHANGELOG.md#404-2023-07-31)
[Compare Source](https://togithub.com/vitejs/vite-plugin-react/compare/v4.0.3...v4.0.4)
- Fix [#198](https://togithub.com/vitejs/vite-plugin-react/discussions/198): Enable Babel if presets list is not empty
### [`v4.0.3`](https://togithub.com/vitejs/vite-plugin-react/blob/HEAD/packages/plugin-react/CHANGELOG.md#403-2023-07-10)
[Compare Source](https://togithub.com/vitejs/vite-plugin-react/compare/v4.0.2...v4.0.3)
- Revert [#108](https://togithub.com/vitejs/vite-plugin-react/pull/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`](https://togithub.com/vitejs/vite-plugin-react/blob/HEAD/packages/plugin-react/CHANGELOG.md#402-2023-07-06)
[Compare Source](https://togithub.com/vitejs/vite-plugin-react/compare/deb40a45f8c296ca2ae4e27c7709bec5ae5b9a62...v4.0.2)
- Fix fast-refresh for files that are transformed into jsx ([#188](https://togithub.com/vitejs/vite-plugin-react/pull/188))
### [`v4.0.1`](https://togithub.com/vitejs/vite-plugin-react/blob/HEAD/packages/plugin-react/CHANGELOG.md#401-2023-06-19)
[Compare Source](https://togithub.com/vitejs/vite-plugin-react/compare/f87d23e91fa48b8a8488dd8bee5277070f5fc3c2...deb40a45f8c296ca2ae4e27c7709bec5ae5b9a62)
- Support [Vitest deps.experimentalOptimizer](https://vitest.dev/config/#deps-experimentaloptimizer)
- Support using components inside web workers ([#181](https://togithub.com/vitejs/vite-plugin-react/pull/181))
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.
This PR contains the following updates:
4.0.0->4.3.1Release Notes
vitejs/vite-plugin-react (@vitejs/plugin-react)
### [`v4.3.1`](https://togithub.com/vitejs/vite-plugin-react/blob/HEAD/packages/plugin-react/CHANGELOG.md#431-2024-06-10) [Compare Source](https://togithub.com/vitejs/vite-plugin-react/compare/v4.3.0...v4.3.1) ##### 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`](https://togithub.com/vitejs/vite-plugin-react/blob/HEAD/packages/plugin-react/CHANGELOG.md#430-2024-05-22) [Compare Source](https://togithub.com/vitejs/vite-plugin-react/compare/v4.2.1...v4.3.0) ##### 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](https://togithub.com/ArnaudBarre/vite-plugin-react-click-to-component) to work, you should update your config to something like: ```ts export default defineConfig(({ command }) => { const babelPlugins = [['babel-plugin-react-compiler', {}]] if (command === 'serve') { babelPlugins.push(['@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. ### [`v4.2.1`](https://togithub.com/vitejs/vite-plugin-react/blob/HEAD/packages/plugin-react/CHANGELOG.md#421-2023-12-04) [Compare Source](https://togithub.com/vitejs/vite-plugin-react/compare/v4.2.0...v4.2.1) Remove generic parameter on `Plugin` to avoid type error with Rollup 4/Vite 5 and `skipLibCheck: false`. I expect very few people to currently use this feature, but if you are extending the React plugin via `api` object, you can get back the typing of the hook by importing `ViteReactPluginApi`: ```ts import type { Plugin } from 'vite' import type { ViteReactPluginApi } from '@vitejs/plugin-react' export const somePlugin: Plugin = { name: 'some-plugin', api: { reactBabel: (babelConfig) => { babelConfig.plugins.push('some-babel-plugin') }, } satisfies ViteReactPluginApi, } ``` ### [`v4.2.0`](https://togithub.com/vitejs/vite-plugin-react/blob/HEAD/packages/plugin-react/CHANGELOG.md#420-2023-11-16) [Compare Source](https://togithub.com/vitejs/vite-plugin-react/compare/v4.1.1...v4.2.0) ##### Update peer dependency range to target Vite 5 There were no breaking change that impacted this plugin, so any combination of React plugins and Vite core version will work. ##### Align jsx runtime for optimized dependencies This will only affect people using internal libraries that contains untranspiled JSX. This change aligns the optimizer with the source code and avoid issues when the published source don't have `React` in the scope. Reminder: While being partially supported in Vite, publishing TS & JSX outside of internal libraries is highly discouraged. ### [`v4.1.1`](https://togithub.com/vitejs/vite-plugin-react/blob/HEAD/packages/plugin-react/CHANGELOG.md#411-2023-11-02) [Compare Source](https://togithub.com/vitejs/vite-plugin-react/compare/v4.1.0...v4.1.1) - Enable retainLines to get correct line numbers for jsxDev (fix [#235](https://togithub.com/vitejs/vite-plugin-react/issues/235)) ### [`v4.1.0`](https://togithub.com/vitejs/vite-plugin-react/blob/HEAD/packages/plugin-react/CHANGELOG.md#410-2023-09-24) [Compare Source](https://togithub.com/vitejs/vite-plugin-react/compare/v4.0.4...v4.1.0) - Add `@types/babel__cores` to dependencies (fix [#211](https://togithub.com/vitejs/vite-plugin-react/issues/211)) - Improve build perf when not using Babel plugins by lazy loading `@babel/core` [#212](https://togithub.com/vitejs/vite-plugin-react/pull/212) - Better invalidation message when an export is added & fix HMR for export of nullish values [#215](https://togithub.com/vitejs/vite-plugin-react/pull/215) - Include non-dev jsx runtime in optimizeDeps & support HMR for JS files using the non dev runtime [#224](https://togithub.com/vitejs/vite-plugin-react/pull/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`](https://togithub.com/vitejs/vite-plugin-react/blob/HEAD/packages/plugin-react/CHANGELOG.md#404-2023-07-31) [Compare Source](https://togithub.com/vitejs/vite-plugin-react/compare/v4.0.3...v4.0.4) - Fix [#198](https://togithub.com/vitejs/vite-plugin-react/discussions/198): Enable Babel if presets list is not empty ### [`v4.0.3`](https://togithub.com/vitejs/vite-plugin-react/blob/HEAD/packages/plugin-react/CHANGELOG.md#403-2023-07-10) [Compare Source](https://togithub.com/vitejs/vite-plugin-react/compare/v4.0.2...v4.0.3) - Revert [#108](https://togithub.com/vitejs/vite-plugin-react/pull/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`](https://togithub.com/vitejs/vite-plugin-react/blob/HEAD/packages/plugin-react/CHANGELOG.md#402-2023-07-06) [Compare Source](https://togithub.com/vitejs/vite-plugin-react/compare/deb40a45f8c296ca2ae4e27c7709bec5ae5b9a62...v4.0.2) - Fix fast-refresh for files that are transformed into jsx ([#188](https://togithub.com/vitejs/vite-plugin-react/pull/188)) ### [`v4.0.1`](https://togithub.com/vitejs/vite-plugin-react/blob/HEAD/packages/plugin-react/CHANGELOG.md#401-2023-06-19) [Compare Source](https://togithub.com/vitejs/vite-plugin-react/compare/f87d23e91fa48b8a8488dd8bee5277070f5fc3c2...deb40a45f8c296ca2ae4e27c7709bec5ae5b9a62) - Support [Vitest deps.experimentalOptimizer](https://vitest.dev/config/#deps-experimentaloptimizer) - Support using components inside web workers ([#181](https://togithub.com/vitejs/vite-plugin-react/pull/181))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.
This PR has been generated by Mend Renovate. View repository job log here.