fix(deps): update all non-major dependencies #41

renovate · 2026-01-24T05:35:38Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@emotion/react (source)	`11.11.1` → `11.14.0`
@emotion/styled (source)	`11.11.0` → `11.14.1`
@fortawesome/free-solid-svg-icons (source)	`6.4.2` → `6.7.2`
@fortawesome/react-fontawesome	`0.2.0` → `0.2.6`
@pretty-cozy/eslint-config	`0.2.0` → `0.7.1`
@types/react (source)	`18.2.18` → `18.3.27`
@types/react-color (source)	`3.0.6` → `3.0.13`
@types/react-dom (source)	`18.2.7` → `18.3.7`
@vitejs/plugin-react (source)	`4.0.4` → `4.7.0`
react (source)	`18.2.0` → `18.3.1`
react-dom (source)	`18.2.0` → `18.3.1`
vite (source)	`4.4.8` → `4.5.14`
vite-plugin-checker	`0.6.1` → `0.12.0`

Release Notes

emotion-js/emotion (@emotion/react)

`v11.14.0`

Compare Source

Minor Changes

#3284 a19d019 Thanks @Andarist! - Source code has been migrated to TypeScript. From now on type declarations will be emitted based on that, instead of being hand-written.

Patch Changes

Updated dependencies [e1bf17e]:
- @emotion/use-insertion-effect-with-fallbacks@1.2.0

`v11.13.5`

Compare Source

Patch Changes

#3270 77d930d Thanks @emmatown! - Fix inconsistent hashes using development vs production bundles/exports conditions when using @emotion/babel-plugin with sourceMap: true (the default). This is particularly visible when using Emotion with the Next.js Pages router where the development condition is used when bundling code but not when importing external code with Node.js.
Updated dependencies [77d930d]:
- @emotion/serialize@1.3.3
- @emotion/utils@1.4.2
- @emotion/babel-plugin@11.13.5

`v11.13.3`

Compare Source

Patch Changes

#3232 0ce3ed0 Thanks @ENvironmentSet! - Distribute css prop attachment over props that are union types
Updated dependencies []:
- @emotion/serialize@1.3.1

`v11.13.0`

Compare Source

Minor Changes

#3198 d8ff8a5 Thanks @Andarist! - Migrated away from relying on process.env.NODE_ENV checks to differentiate between production and development builds.

Development builds (and other environment-specific builds) can be used by using proper conditions (see here). Most modern bundlers/frameworks already preconfigure those for the user so no action has to be taken.

Default files should continue to work in all environments.
#3215 a9f6912 Thanks @Andarist! - Added edge-light and workerd conditions to package.json manifest to better serve users using Vercel Edge and Cloudflare Workers.

Patch Changes

Updated dependencies [d8ff8a5, a9f6912]:
- @emotion/serialize@1.3.0
- @emotion/use-insertion-effect-with-fallbacks@1.1.0
- @emotion/utils@1.4.0

`v11.12.0`

Compare Source

Patch Changes

#3206 d1994c4 Thanks @DiegoAndai! - Improved compatibility with the upcoming @types/react for React 19 where the global JSX namespace doesn't exist anymore
#3208 56109e7 Thanks @Andarist! - Only forward defined refs to improve compatibility with the upcoming React 19
Updated dependencies [9ca22c6, a1e881b, 16d8a8c]:
- @emotion/serialize@1.2.0
- @emotion/is-prop-valid@1.3.0
- @emotion/utils@1.3.0
- @emotion/babel-plugin@11.12.0

`v11.11.4`

Compare Source

Patch Changes

#3159 5b82631d Thanks @iegik! - Renamed an internal hasOwnProperty to hasOwn. This avoids problems in CommonJS environments when the consumer tries to prevent prototype pollution with Object.freeze(Object.prototype).

`v11.11.3`

Compare Source

Patch Changes

#3101 49c20b4f Thanks @kyvong! - Fix Theme import for newer Typescript module resolution modes
Updated dependencies [45c440fb]:
- @emotion/serialize@1.1.3

FortAwesome/Font-Awesome (@fortawesome/free-solid-svg-icons)

FortAwesome/react-fontawesome (@fortawesome/react-fontawesome)

`v0.2.6`

Compare Source

Fixed

check for existence of process before reading process.env (#585)

Full Changelog: FortAwesome/react-fontawesome@0.2.5...0.2.6

`v0.2.5`

Compare Source

What's Changed

#583 - fix interface definition by @dom-the-dev in #584

New Contributors

@dom-the-dev made their first contribution in #584

Full Changelog: FortAwesome/react-fontawesome@0.2.4...0.2.5

`v0.2.3`

Compare Source

Changed

Font Awesome Pro+ icons are now available with an active Pro+ subscription.
Removed example directory and files
Deprecated fa-fw prop

Added

Added widthAuto prop
Added rotateBy prop

`v0.2.2`

Compare Source

Fixed

Props with nullable/undefined values no longer throw an error #562 #560

`v0.2.1`

Compare Source

Changed

Remove defaultProps to be compatible with React 19

PrettyCoffee/pretty-cozy (@pretty-cozy/eslint-config)

`v0.7.1`

Compare Source

`v0.7.0`

Compare Source

`v0.6.0`

Compare Source

`v0.5.1`

Compare Source

`v0.5.0`

Compare Source

`v0.4.0`

Compare Source

`v0.3.1`

Compare Source

`v0.3.0`

Compare Source

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

`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)

facebook/react (react)

`v18.3.1`

Compare Source

Export act from react f1338f

`v18.3.0`

Compare Source

This release is identical to 18.2 but adds warnings for deprecated APIs and other changes that are needed for React 19.

Read the React 19 Upgrade Guide for more info.

React

Allow writing to this.refs to support string ref codemod 909071
Warn for deprecated findDOMNode outside StrictMode c3b283
Warn for deprecated test-utils methods d4ea75
Warn for deprecated Legacy Context outside StrictMode 415ee0
Warn for deprecated string refs outside StrictMode #25383
Warn for deprecated defaultProps for function components #25699
Warn when spreading key #25697
Warn when using act from test-utils d4ea75

React DOM

Warn for deprecated unmountComponentAtNode 8a015b
Warn for deprecated renderToStaticNodeStream #28874

vitejs/vite (vite)