Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 10, 2024

This PR contains the following updates:

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

Release Notes

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

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
export default defineConfig(({ command }) => {
  const babelPlugins = [['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:

export default defineConfig(({ command }) => {
  const babelPlugins = [['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: 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch from a4f725d to 81dea34 Compare August 28, 2024 07:51
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch from 81dea34 to 0170983 Compare September 29, 2024 22:15
@renovate renovate bot changed the title chore(deps): update dependency @vitejs/plugin-react to v4.3.1 chore(deps): update dependency @vitejs/plugin-react to v4.3.2 Sep 29, 2024
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch from 0170983 to 46e3bc2 Compare October 9, 2024 08:37
@renovate renovate bot changed the title chore(deps): update dependency @vitejs/plugin-react to v4.3.2 chore(deps): update dependency @vitejs/plugin-react to v4.3.3 Oct 19, 2024
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch 2 times, most recently from 8f4fc44 to 60a200f Compare October 26, 2024 09:47
@renovate renovate bot changed the title chore(deps): update dependency @vitejs/plugin-react to v4.3.3 chore(deps): update dependency @vitejs/plugin-react to v4.3.4 Nov 26, 2024
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x-lockfile branch from 60a200f to 587d094 Compare November 26, 2024 11:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants