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 #599

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 20, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitejs/plugin-react (source) 3.1.0 -> 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.

v4.2.1

Compare Source

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:

import type { Plugin } from 'vite'
import type { ViteReactPluginApi } from '@&#8203;vitejs/plugin-react'

export const somePlugin: Plugin = {
  name: 'some-plugin',
  api: {
    reactBabel: (babelConfig) => {
      babelConfig.plugins.push('some-babel-plugin')
    },
  } satisfies ViteReactPluginApi,
}

v4.2.0

Compare Source

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

Compare Source

  • Enable retainLines to get correct line numbers for jsxDev (fix #​235)

v4.1.0

Compare Source

  • Add @types/babel__cores to dependencies (fix #​211)
  • Improve build perf when not using Babel plugins by lazy loading @babel/core #​212
  • Better invalidation message when an export is added & fix HMR for export of nullish values #​215
  • Include non-dev jsx runtime in optimizeDeps & support HMR for JS files using the non dev runtime #​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

Compare Source

  • Fix #​198: Enable Babel if presets list is not empty

v4.0.3

Compare Source

  • Revert #​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

Compare Source

  • Fix fast-refresh for files that are transformed into jsx (#​188)

v4.0.1

Compare Source

v4.0.0

Compare Source

This major version include a revamp of options:

  • include/exclude now allow to completely override the files processed by the plugin (#​122). This is more in line with other Rollup/Vite plugins and simplify the setup of enabling Fast Refresh for .mdx files. This can be done like this:
export default defineConfig({
  plugins: [
    { enforce: 'pre', ...mdx() },
    react({ include: /\.(mdx|js|jsx|ts|tsx)$/ }),
  ],
})

These changes also allow to apply Babel plugins on files outside Vite root (expect in node_modules), which improve support for monorepo (fix #​16).

With these changes, only the file extensions is used for filtering processed files and the query param fallback is removed.

  • fastRefresh is removed (#​122). This should be correctly activated by plugin without configuration.
  • jsxPure is removed. This is a niche use case that was just passing down the boolean to esbuild.jsxSideEffects. (#​129)

The support for React auto import whe using classic runtime is removed. This was prone to errors and added complexity for no good reason given the very wide support of automatic runtime nowadays. This migration path should be as simple as removing the runtime option from the config.

This release goes in hand with the upcoming Vite 4.3 release focusing on performances:

  • Cache plugin load (#​141)
  • Wrap dynamic import to speedup analysis (#​143)

Other notable changes:

  • Silence "use client" warning (#​144, fix #​137)
  • Fast Refresh is applied on JS files using automatic runtime (#​122, fix #​83)
  • Vite 4.2 is required as a peer dependency (#​128)
  • Avoid key collision in React refresh registration (a74dfef, fix #​116)
  • Throw when refresh runtime is loaded twice (#​108, fix #​101)
  • Don't force optimization of jsx-runtime (#​132)

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.

@socket-security
Copy link

socket-security bot commented Apr 20, 2023

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

View full report↗︎

@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch 4 times, most recently from 0b8677b to 7570816 Compare April 26, 2023 19:25
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch 3 times, most recently from 3b57435 to aaa100c Compare May 5, 2023 10:35
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch 2 times, most recently from 281d3ff to 52c3190 Compare May 15, 2023 15:07
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch 3 times, most recently from b6a3b4d to 6bf9a9d Compare May 18, 2023 12:55
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch 3 times, most recently from 4e1c957 to 09fbc86 Compare May 29, 2023 17:34
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch from 09fbc86 to ea00153 Compare June 5, 2023 19:27
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch from ea00153 to 94a4d19 Compare June 14, 2023 18:31
@socket-security
Copy link

socket-security bot commented Jun 14, 2023

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@vitejs/[email protected] Transitive: environment, filesystem, shell, unsafe +55 16.1 MB antfu, patak, soda, ...2 more

🚮 Removed packages: npm/@vitejs/[email protected]

View full report↗︎

@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch 3 times, most recently from 700c773 to 3b36783 Compare June 26, 2023 18:26
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch 5 times, most recently from 86cc999 to d62501f Compare July 10, 2023 08:29
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch 3 times, most recently from 94fdafd to e52cce9 Compare July 14, 2023 11:06
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch 3 times, most recently from df3aee4 to 0d98ed4 Compare July 24, 2023 16:20
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch 3 times, most recently from 17914bf to 20ced04 Compare August 7, 2023 09:25
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch from 20ced04 to 2427008 Compare August 13, 2023 19:25
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch 2 times, most recently from f3786c5 to 00687ff Compare September 24, 2023 19:09
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch 2 times, most recently from 4ba0e25 to a5cd4c4 Compare October 5, 2023 09:05
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch 2 times, most recently from db6ec59 to caa65ed Compare October 20, 2023 23:23
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch from caa65ed to 4d264fe Compare November 2, 2023 11:28
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch from 4d264fe to 139c7af Compare November 16, 2023 14:36
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch from 139c7af to 646072f Compare December 4, 2023 19:57
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch from 646072f to eaa193c Compare May 4, 2024 09:56
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch from eaa193c to 2997db9 Compare May 22, 2024 22:03
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch from 2997db9 to 0603179 Compare June 10, 2024 00:49
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch from 0603179 to 56624df Compare September 29, 2024 22:19
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch from 56624df to 6f94295 Compare October 19, 2024 18:07
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch from 6f94295 to 1f9e4cd Compare October 29, 2024 12:56
@renovate renovate bot force-pushed the renovate/vitejs-plugin-react-4.x branch from 1f9e4cd to eee184a Compare November 26, 2024 15:03
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