mammadataei / cypress-vite

Run Cypress specs using Vite
MIT License
85 stars 10 forks source link

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

Open renovate[bot] opened 6 months ago

renovate[bot] commented 6 months ago

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitejs/plugin-react (source) 4.2.0 -> 4.3.1 age adoption passing confidence

Release 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, } ```

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 was generated by Mend Renovate. View the repository job log.