Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Apr 8, 2024

This PR contains the following updates:

Package Change Age Confidence Type Update Pending
@types/react (source) ^18.0.24 -> ^19.0.0 age confidence devDependencies major 19.2.7 (+1)
@types/react-dom (source) ^18.0.8 -> ^19.0.0 age confidence devDependencies major
@vitejs/plugin-react (source) ^2.2.0 -> ^5.0.0 age confidence devDependencies major
actions/checkout v3 -> v5 age confidence action major v6
actions/setup-node v3 -> v6 age confidence action major
chai (source) 4.3.6 -> 6.2.1 age confidence devDependencies major
jsdom ^20.0.3 -> ^27.0.0 age confidence dependencies major
node 14 -> 24 age confidence uses-with major
react (source) ^18.2.0 -> ^19.0.0 age confidence dependencies major
react-dom (source) ^18.2.0 -> ^19.0.0 age confidence dependencies major
rimraf ^3.0.2 -> ^6.0.0 age confidence devDependencies major 6.1.2 (+1)
sinon (source) 14.0.1 -> 21.0.0 age confidence devDependencies major
stylelint (source) 14.13.0 -> 16.25.0 age confidence devDependencies major 16.26.1 (+1)
stylelint-config-standard 25.0.0 -> 39.0.1 age confidence devDependencies major
vite (source) ^3.2.3 -> ^7.0.0 age confidence devDependencies major 7.2.4 (+1)
webpack-cli (source) ^5.0.1 -> ^6.0.0 age confidence devDependencies major
wrangler (source) 2.5.0 -> 4.48.0 age confidence devDependencies major 4.51.0 (+3)

Release Notes

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

v5.1.1

Compare Source

Update code to support newer rolldown-vite (#​976)

rolldown-vite will remove optimizeDeps.rollupOptions in favor of optimizeDeps.rolldownOptions soon. This plugin now uses optimizeDeps.rolldownOptions to support newer rolldown-vite. Please update rolldown-vite to the latest version if you are using an older version.

v5.1.0

Compare Source

Add @vitejs/plugin-react/preamble virtual module for SSR HMR (#​890)

SSR applications can now initialize HMR runtime by importing @vitejs/plugin-react/preamble at the top of their client entry instead of manually calling transformIndexHtml. This simplifies SSR setup for applications that don't use the transformIndexHtml API.

Fix raw Rolldown support for Rolldown 1.0.0-beta.44+ (#​930)

Rolldown 1.0.0-beta.44+ removed the top-level jsx option in favor of transform.jsx. This plugin now uses the transform.jsx option to support Rolldown 1.0.0-beta.44+.

v5.0.4

Compare Source

Perf: use native refresh wrapper plugin in rolldown-vite (#​881)

v5.0.3

Compare Source

HMR did not work for components imported with queries with rolldown-vite (#​872)
Perf: simplify refresh wrapper generation (#​835)

v5.0.2

Compare Source

Skip transform hook completely in rolldown-vite in dev if possible (#​783)

v5.0.1

Compare Source

Set optimizeDeps.rollupOptions.transform.jsx instead of optimizeDeps.rollupOptions.jsx for rolldown-vite (#​735)

optimizeDeps.rollupOptions.jsx is going to be deprecated in favor of optimizeDeps.rollupOptions.transform.jsx.

Perf: skip babel-plugin-react-compiler if code has no "use memo" when { compilationMode: "annotation" } (#​734)
Respect tsconfig jsxImportSource (#​726)
Fix reactRefreshHost option on rolldown-vite (#​716)
Fix RefreshRuntime being injected twice for class components on rolldown-vite (#​708)
Skip babel-plugin-react-compiler on non client environment (689)

v5.0.0

Compare Source

v4.7.0

Compare Source

Add HMR support for compound components (#​518)

HMR now works for compound components like this:

const Root = () => <div>Accordion Root</div>
const Item = () => <div>Accordion Item</div>

export const Accordion = { 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 errors
react({ 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
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)

v3.1.0

Compare Source

  • doc: add jsxImportSource option (38d71f6)
  • chore: bump release-scripts, typecheck package in CI, remove cache for eslint (9af763d)
  • fix: fast-refresh explain link (#​97) (6097795), closes #​97

v3.0.1

Compare Source

v3.0.0

Compare Source

actions/checkout (actions/checkout)

v5

Compare Source

v4

Compare Source

actions/setup-node (actions/setup-node)

v6

Compare Source

v5

Compare Source

v4

Compare Source

chaijs/chai (chai)

v6.2.1

Compare Source

What's Changed

New Contributors

Full Changelog: chaijs/chai@v6.2.0...v6.2.1

v6.2.0

Compare Source

What's Changed

Full Changelog: chaijs/chai@v6.1.0...v6.2.0

v6.1.0

Compare Source

What's Changed

  • build(deps-dev): bump tar-fs from 3.0.9 to 3.1.1 by @​dependabot[bot] in #​1706
  • feat: add eventEmitter (#​1693)
    Adds an event emitter for hooking into method/property creation in #​1693

Full Changelog: chaijs/chai@v6.0.2...v6.1.0

v6.0.1

Compare Source

What's Changed

Full Changelog: chaijs/chai@v6.0.0...v6.0.1

v6.0.0

Compare Source

BREAKING CHANGES

Chai is now bundled into a single file. The lib/*.js files are no longer present, and so any code that imports those files directly will need to change. The only file that can be imported now is ./index.js.

What's Changed

Full Changelog: chaijs/chai@v5.3.2...v6.0.0

v5.3.3

Compare Source

What's Changed

Full Changelog: chaijs/chai@v5.3.2...v5.3.3

v5.3.2

Compare Source

Reverts the removal of the bundled version of chai in 5.3.1

What's Changed

Full Changelog: chaijs/chai@v5.3.1...v5.3.2

v5.3.1

Compare Source

What's Changed

Full Changelog: chaijs/chai@v5.3.0...v5.3.1

v5.3.0

Compare Source

What's Changed

Full Changelog: chaijs/chai@v5.2.2...v5.3.0

v5.2.2

Compare Source

What's Changed

Full Changelog: chaijs/chai@v5.2.1...v5.2.2

v5.2.1

Compare Source

What's Changed

Mostly internal changes but @​SuperchupuDev realised the package.json engines field was out of date, so it has been updated to reflect that v5.0.0 onwards only supports Node >=18.

New Contributors

Full Changelog: chaijs/chai@v5.2.0...v5.2.1

v5.2.0

Compare Source

What's Changed

New Contributors

Full Changelog: chaijs/chai@v5.1.2...v5.2.0

v5.1.2

Compare Source

What's Changed

Full Changelog: chaijs/chai@v5.1.1...v5.1.2

v5.1.1

Compare Source

What's Changed

New Contributors

Full Changelog: chaijs/chai@v5.1.0...v5.1.1

v5.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: chaijs/chai@v5.0.3...v5.1.0

v5.0.3

Compare Source

Fix bad v5.0.2 publish.

Full Changelog: chaijs/chai@v5.0.2...v5.0.3

v5.0.2

Compare Source

What's Changed

Full Changelog: chaijs/chai@v5.0.1...v5.0.2

v5.0.0

Compare Source

BREAKING CHANGES

  • Chai now only supports EcmaScript Modules (ESM). This means your tests will need to either have import {...} from 'chai' or import('chai'). require('chai') will cause failures in nodejs. If you're using ESM and seeing failures, it may be due to a bundler or transpiler which is incorrectly converting import statements into require calls.
  • Dropped support for Internet Explorer.
  • Dropped support for NodeJS < 18.
  • Minimum supported browsers are now Firefox 100, Safari 14.1, Chrome 100, Edge 100. Support for browsers prior to these versions is "best effort" (bug reports on older browsers will be assessed individually and may be marked as wontfix).

What's Changed


Configuration

📅 Schedule: Branch creation - "after 2pm on Monday" in timezone Europe/Zurich, 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@aem-code-sync
Copy link

aem-code-sync bot commented Apr 8, 2024

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
In case there are problems, just click a checkbox below to rerun the respective action.

  • Re-run PSI checks
  • Re-sync branch
Commits

@renovate renovate bot force-pushed the renovate-major-external-major branch from a46c829 to bcaea9b Compare April 13, 2024 08:58
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major April 13, 2024 08:58 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from bcaea9b to 5c2c072 Compare April 18, 2024 02:39
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major April 18, 2024 02:39 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from 5c2c072 to c9ecc51 Compare April 19, 2024 17:45
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major April 19, 2024 17:45 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from c9ecc51 to d4bfda2 Compare April 23, 2024 23:23
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major April 23, 2024 23:23 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from d4bfda2 to ce5aae9 Compare April 24, 2024 17:49
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major April 24, 2024 17:49 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch 2 times, most recently from 3997f49 to 85e715f Compare May 2, 2024 14:59
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major May 2, 2024 14:59 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from 85e715f to b217049 Compare May 3, 2024 05:36
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major May 3, 2024 05:36 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from b217049 to 413bd00 Compare May 8, 2024 23:45
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major May 8, 2024 23:45 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from 413bd00 to 6cc2915 Compare May 9, 2024 20:56
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major May 9, 2024 20:57 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from 6cc2915 to bc3c7ce Compare May 13, 2024 21:03
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major May 13, 2024 21:03 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch 2 times, most recently from 0ad1adc to 11ebf1f Compare May 25, 2024 05:00
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major May 25, 2024 05:00 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from 11ebf1f to 3ad4936 Compare May 29, 2024 02:52
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major May 29, 2024 02:52 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from 3ad4936 to 939a6ee Compare May 31, 2024 17:42
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major May 31, 2024 17:42 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from 939a6ee to b85a18a Compare June 4, 2024 18:00
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major October 13, 2025 20:04 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from ae5aedc to f4308df Compare October 15, 2025 23:39
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major October 15, 2025 23:39 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from f4308df to f8d9811 Compare October 17, 2025 04:10
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major October 17, 2025 04:10 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from f8d9811 to 03b88ed Compare October 18, 2025 15:50
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major October 18, 2025 15:50 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from 03b88ed to c0bdafb Compare October 21, 2025 03:31
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major October 21, 2025 03:31 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from c0bdafb to ebd39ad Compare October 25, 2025 20:00
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major October 25, 2025 20:00 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from ebd39ad to 76566c0 Compare November 2, 2025 07:57
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major November 2, 2025 07:57 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from 76566c0 to 01a452e Compare November 8, 2025 23:51
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major November 8, 2025 23:51 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from 01a452e to 49c249c Compare November 15, 2025 12:15
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major November 15, 2025 12:15 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from 49c249c to 4576402 Compare November 19, 2025 04:01
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major November 19, 2025 04:01 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from 4576402 to 105b668 Compare November 20, 2025 15:51
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major November 20, 2025 15:51 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from 105b668 to df95024 Compare November 22, 2025 11:46
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major November 22, 2025 11:46 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from df95024 to ced200a Compare November 25, 2025 23:59
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major November 25, 2025 23:59 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from ced200a to 2fe0914 Compare November 27, 2025 20:02
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major November 27, 2025 20:02 Inactive
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.

1 participant