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

renovate · 2024-12-02T01:38:47Z

This PR contains the following updates:

Package	Change	Type	Update
@babel/core (source)	`^7.26.0` -> `^7.26.10`	dependencies	patch
@babel/plugin-proposal-pipeline-operator (source)	`^7.25.9` -> `^7.26.7`	devDependencies	minor
@emotion/react (source)	`^11.13.5` -> `^11.14.0`	dependencies	minor
@emotion/styled (source)	`^11.13.5` -> `^11.14.0`	dependencies	minor
@types/node (source)	`^20.17.7` -> `^20.17.28`	devDependencies	patch
@types/react (source)	`^18.3.12` -> `^18.3.20`	devDependencies	patch
@types/react-dom (source)	`^18.3.1` -> `^18.3.5`	devDependencies	patch
@vitejs/release-scripts	`^1.3.2` -> `^1.4.0`	devDependencies	minor
eslint-plugin-n	`^17.14.0` -> `^17.17.0`	devDependencies	minor
fs-extra	`^11.2.0` -> `^11.3.0`	devDependencies	minor
lint-staged	`^15.2.10` -> `^15.5.0`	devDependencies	minor
playwright-chromium (source)	`^1.49.0` -> `^1.51.1`	devDependencies	minor
pnpm (source)	`10.6.5` -> `10.7.0`	packageManager	minor
pnpm/action-setup	`v4.0.0` -> `v4.1.0`	action	minor
react (source)	`^19.0.0-rc-fb9a90fa48-20240614` -> `^19.1.0`	dependencies	minor
react-dom (source)	`^19.0.0-rc-fb9a90fa48-20240614` -> `^19.1.0`	dependencies	minor
react-refresh (source)	`^0.14.2` -> `^0.17.0`	dependencies	minor
react-switch	`^7.0.0` -> `^7.1.0`	dependencies	minor
simple-git-hooks	`^2.11.1` -> `^2.12.1`	devDependencies	minor
tsx (source)	`^4.19.2` -> `^4.19.3`	devDependencies	patch
typescript (source)	`^5.7.2` -> `^5.8.2`	devDependencies	minor
vite (source)	`^6.0.0` -> `^6.2.3`	devDependencies	minor
vitest (source)	`^3.0.4` -> `^3.0.9`	devDependencies	patch

Release Notes

babel/babel (@babel/core)

`v7.26.10`

Compare Source

👓 Spec Compliance

babel-parser
- #17159 Disallow decorator in array pattern (@JLHwung)

🐛 Bug Fix

babel-parser, babel-template
- #17164 Fix: always initialize ExportDeclaration attributes (@JLHwung)
babel-core
- #17142 fix: "Map maximum size exceeded" in deepClone (@liuxingbaoyu)
babel-parser, babel-plugin-transform-typescript
- #17154 Update typescript parser tests (@JLHwung)
babel-traverse
- #17151 fix: Should not evaluate vars in child scope (@liuxingbaoyu)
babel-generator
- #17153 fix: Correctly generate abstract override (@liuxingbaoyu)
babel-parser
- #17107 Fix source type detection when parsing TypeScript (@JLHwung)
babel-helpers, babel-runtime, babel-runtime-corejs2, babel-runtime-corejs3
- #17173 Fix processing of replacement pattern with named capture groups (@mmmsssttt404)

💅 Polish

babel-standalone
- #17158 Avoid warnings when re-bundling @babel/standalone with webpack (@liuxingbaoyu)

🏠 Internal

babel-parser
- #17160 Left-value parsing cleanup (@JLHwung)

`v7.26.9`

Compare Source

🐛 Bug Fix

babel-types
- #17103 fix: Definition for TSPropertySignature.kind (@liuxingbaoyu)
babel-generator, babel-types
- #17062 Print TypeScript optional/definite in ClassPrivateProperty (@jamiebuilds-signal)

🏠 Internal

babel-types
- #17130 Use .ts files with explicit reexports to solve name conflicts (@nicolo-ribaudo)
babel-core
- #17127 Do not depend on @types/gensync in Babel 7 (@nicolo-ribaudo)

`v7.26.8`

Compare Source

v7.26.8 (2025-02-08)

🏠 Internal

babel-preset-env
- #17097 Update dependency babel-plugin-polyfill-corejs3 to ^0.11.0

`v7.26.7`

Compare Source

🐛 Bug Fix

babel-helpers, babel-preset-env, babel-runtime-corejs3
- #17086 Make "object without properties" helpers ES6-compatible (@tquetano-netflix)
babel-plugin-transform-typeof-symbol
- #17085 fix: Correctly handle typeof in arrow functions (@liuxingbaoyu)
babel-parser
- #17079 Respect ranges option in estree method value (@JLHwung)
babel-core
- #17052 Do not try to parse .ts configs as JSON if natively supported (@nicolo-ribaudo)
babel-plugin-transform-typescript
- #17050 fix: correctly resolve references to non-constant enum members (@branchseer)
babel-plugin-transform-typescript, babel-traverse, babel-types
- #17025 fix: Remove type-only import x = y.z (@liuxingbaoyu)

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

vitejs/release-scripts (@vitejs/release-scripts)

`v1.4.0`

Compare Source

`v1.3.3`

Compare Source

eslint-community/eslint-plugin-n (eslint-plugin-n)

`v17.17.0`

Compare Source

🌟 Features

allow-modules: include virtual: in the modules pattern (#425) (a109793)
node-builtin: Add support for import.meta properties (#420) (76fc219)

🩹 Fixes

no-unpublished: allowModules option was disabled when using TS alias (#423) (9ae39fb)
type errors (#427) (8e3c290)

`v17.16.2`

Compare Source

🩹 Fixes

Revert "feat: add support for ignoring sync methods from certain locations" (#416) (0779e2f)

`v17.16.1`

Compare Source

🩹 Fixes

patch new eslint options types (#411) (340312e)

🧹 Chores

package: explicitly declare js module type (#410) (9f09931)

`v17.15.1`

Compare Source

🩹 Fixes

Promise.withResolvers is supported since node 22.11 (#398) (c5bcb3a)

`v17.15.0`

Compare Source

🌟 Features

no-unsupported: support node 22.12.0 (#393) (af4f774)
resolve: allow overriding enhanced-resolve's options (#384) (1466bec)

🩹 Fixes

no-unsupported: Correctly handle recursive objects on a per module basis (#396) (db384d1)

jprichardson/node-fs-extra (fs-extra)

`v11.3.0`

Compare Source

Add promise support for newer fs methods (#1044, #1045)
Use fs.opendir in copy()/copySync() for better perf/scalability (#972, #1028)

lint-staged/lint-staged (lint-staged)

`v15.5.0`

Compare Source

Minor Changes

#1526 630af5f Thanks @iiroj! - Lint-staged no longer resets to the original state when preventing an empty git commit. This happens when your configured tasks reset all the staged changes, typically when trying to commit formatting changes which conflict with your linter setup like ESLint or Prettier.

Example with Prettier

By default Prettier prefers double quotes.

Previously

Stage file.js with only double quotes " changed to '
Run git commit -am "I don't like double quotes"
Lint-staged runs prettier --write file.js, converting all the ' back to "
Because there are now no changes, lint-staged fails, cancels the commit, and resets back to the original state
Commit was not done, original state is restored and single quotes ' are staged

Now

Stage file.js with only double-quotes " changed to '
Run git commit -am "I don't like double quotes"
Lint-staged runs prettier --write file.js, converting all the ' back to "
Because there are now no changes, lint-staged fails and cancels the commit
Commit was not done, and there are no staged changes

`v15.4.3`

Compare Source

Patch Changes

#1512 cbfed1d Thanks @tarik02! - Adjust TypeScript types for the default export so that it can be used as a value without error TS2693.

`v15.4.2`

Compare Source

Patch Changes

#1509 8827ebf Thanks @iiroj! - Change lint-staged's dependencies to use caret (^) ranges instead of tilde (~). This makes it easier for package managers to perform dependency management when minor-level updates are also permitted instead of just patch-level.

`v15.4.1`

Compare Source

Patch Changes

#1504 1c7a45e Thanks @iiroj! - Default TypeScript config filenames match JS equivalents.
#1504 9cc18c9 Thanks @iiroj! - Add missing conditional exports syntax for TypeScript types.

`v15.4.0`

Compare Source

Minor Changes

#1500 a8ec1dd Thanks @iiroj! - Lint-staged now provides TypeScript types for the configuration and main Node.js API. You can use the JSDoc syntax in your JS configuration files:
```
/**
 * @&#8203;filename: lint-staged.config.js
 * @&#8203;type {import('lint-staged').Configuration}
 */
export default {
  '*': 'prettier --write',
}
```
It's also possible to use the .ts file extension for the configuration if your Node.js version supports it. The --experimental-strip-types flag was introduced in Node.js v22.6.0 and unflagged in v23.6.0, enabling Node.js to execute TypeScript files without additional configuration.
```
export NODE_OPTIONS="--experimental-strip-types"

npx lint-staged --config lint-staged.config.ts
```

Patch Changes

#1501 9b79364 Thanks @iiroj! - Handle possible failures when logging user shell for debug info.

`v15.3.0`

Compare Source

Minor Changes

#1495 e69da9e Thanks @iiroj! - Added more info to the debug logs so that "environment" info doesn't need to be added separately to GitHub issues.
#1493 fa0fe98 Thanks @iiroj! - Added more help messages around the automatic git stash that lint-staged creates as a backup (by default). The console output also displays the short git hash of the stash so that it's easier to recover lost files in case some fatal errors are encountered, or the process is killed before completing.

For example:
```
% npx lint-staged
✔ Backed up original state in git stash (20addf8)
✔ Running tasks for staged files...
✔ Applying modifications from tasks...
✔ Cleaning up temporary files...
```
where the backup can be seen with git show 20addf8, or git stash list:
```
% git stash list
stash@{0}: lint-staged automatic backup (20addf8)
```

`v15.2.11`

Compare Source

Patch Changes

#1484 bcfe309 Thanks @wormsik! - Escape paths containing spaces when using the "shell" option.
#1487 7dd8caa Thanks @iiroj! - Do not treat submodule root paths as "staged files". This caused lint-staged to fail to a Git error when only updating the revision of a submodule.

microsoft/playwright (playwright-chromium)

`v1.51.1`

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/35093 - [Regression]: TimeoutOverflowWarning: 2149630.634 does not fit into a 32-bit signed integer
https://github.com/microsoft/playwright/issues/35138 - [Regression]: TypeError: Cannot read properties of undefined (reading 'expectInfo')

Browser Versions

Chromium 134.0.6998.35
Mozilla Firefox 135.0
WebKit 18.4

This version was also tested against the following stable channels:

Google Chrome 133
Microsoft Edge 133

`v1.51.0`

Compare Source

`v1.50.1`

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/34483 - [Feature]: single aria snapshot for different engines/browsershttps://github.com/microsoft/playwright/issues/344977 - [Bug]: Firefox not handling keepalive: true fetch requesthttps://github.com/microsoft/playwright/issues/3450404 - [Bug]: update snapshots not creating good difhttps://github.com/microsoft/playwright/issues/34507507 - [Bug]: snapshotPathTemplate doesnt work when multiple projehttps://github.com/microsoft/playwright/issues/344624462 - [Bug]: updateSnapshots "changed" throws an error

Browser Versions

Chromium 133.0.6943.16
Mozilla Firefox 134.0
WebKit 18.2

This version was also tested against the following stable channels:

Google Chrome 132
Microsoft Edge 132

`v1.50.0`

Compare Source

Test runner

New option timeout allows specifying a maximum run time for an individual test step. A timed-out step will fail the execution of the test.

test('some test', async ({ page }) => {
  await test.step('a step', async () => {
    // This step can time out separately from the test
  }, { timeout: 1000 });
});

New method test.step.skip() to disable execution of a test step.

test('some test', async ({ page }) => {
  await test.step('before running step', async () => {
    // Normal step
  });

  await test.step.skip('not yet ready', async () => {
    // This step is skipped
  });

  await test.step('after running step', async () => {
    // This step still runs even though the previous one was skipped
  });
});

Expanded expect(locator).toMatchAriaSnapshot() to allow storing of aria snapshots in separate YAML files.
Added method expect(locator).toHaveAccessibleErrorMessage() to assert the Locator points to an element with a given aria errormessage.
Option testConfig.updateSnapshots added the configuration enum changed. changed updates only the snapshots that have changed, whereas all now updates all snapshots, regardless of whether there are any differences.
New option testConfig.updateSourceMethod defines the way source code is updated when testConfig.updateSnapshots is configured. Added overwrite and 3-way modes that write the changes into source code, on top of existing patch mode that creates a patch file.
```
npx playwright test --update-snapshots=changed --update-source-method=3way
```
Option testConfig.webServer added a gracefulShutdown field for specifying a process kill signal other than the default SIGKILL.
Exposed testStep.attachments from the reporter API to allow retrieval of all attachments created by that step.
New option pathTemplate for toHaveScreenshot and toMatchAriaSnapshot assertions in the testConfig.expect configuration.

UI updates

Updated default HTML reporter to improve display of attachments.
New button for picking elements to produce aria snapshots.
Additional details (such as keys pressed) are now displayed alongside action API calls in traces.
Display of canvas content in traces is error-prone. Display is now disabled by default, and can be enabled via the Display canvas content UI setting.
Call and Network panels now display additional time information.

Breaking

expect(locator).toBeEditable() and locator.isEditable() now throw if the target element is not <input>, <select>, or a number of other editable elements.
Option testConfig.updateSnapshots now updates all snapshots when set to all, rather than only the failed/changed snapshots. Use the new enum changed to keep the old functionality of only updating the changed snapshots.

Browser Versions

Chromium 133.0.6943.16
Mozilla Firefox 134.0
WebKit 18.2

This version was also tested against the following stable channels:

Google Chrome 132
Microsoft Edge 132

`v1.49.1`

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/33802 - [Bug]: Codegen's Clear button doesn't work if not recordinghttps://github.com/microsoft/playwright/issues/338066 - [Bug]: playwright hangs while waiting for pending navigationhttps://github.com/microsoft/playwright/issues/3378787 - [Bug]: VSC extension isn't capturing all entered tehttps://github.com/microsoft/playwright/issues/33788788 - [Regression]: Double clicking the steps in trace viewer doesn't filter actihttps://github.com/microsoft/playwright/issues/337723772 - [Bug]: aria_snapshot generates invalid yaml when combined with an aria-label attrhttps://github.com/microsoft/playwright/issues/3379133791 - [Bug]: text input with number value raises "container is not iterable" with to_match_aria_snahttps://github.com/microsoft/playwright/issues/33644/33644 - [Bug]: getByRole can't find element with the accessible name from label element when aria-labelledby is nothttps://github.com/microsoft/playwright/issues/33660s/33660 - [Regression]: Unable to open Playwright UI in Dark Mode

Browser Versions

Chromium 131.0.6778.33
Mozilla Firefox 132.0
WebKit 18.2

This version was also tested against the following stable channels:

Google Chrome 130
Microsoft Edge 130

pnpm/pnpm (pnpm)

`v10.7.0`

Compare Source

Minor Changes

pnpm config get and list also show settings set in pnpm-workspace.yaml files #9316.
It should be possible to use env variables in pnpm-workspace.yaml setting names and value.
Add an ability to patch dependencies by version ranges. Exact versions override version ranges, which in turn override name-only patches. Version range * is the same as name-only, except that patch application failure will not be ignored.

For example:
```
patchedDependencies:
  foo: patches/foo-1.patch
  foo@^2.0.0: patches/foo-2.patch
  [email protected]: patches/foo-3.patch
```
The above configuration would apply patches/foo-3.patch to [email protected], patches/foo-2.patch to all foo versions which satisfy ^2.0.0 except 2.1.0, and patches/foo-1.patch to the remaining foo versions.
[!WARNING]
The version ranges should not overlap. If you want to specialize a sub range, make sure to exclude it from the other keys. For example:
```
# pnpm-workspace.yaml
patchedDependencies:
  # the specialized sub range
  '[email protected]': patches/foo.2.2.0-2.8.0.patch
  # the more general patch, excluding the sub range above
  'foo@>=2.0.0 <2.2.0 || >2.8.0': 'patches/foo.gte2.patch
```
In most cases, however, it's sufficient to just define an exact version to override the range.
pnpm config set --location=project saves the setting to a pnpm-workspace.yaml file if no .npmrc file is present in the directory #9316.
Rename pnpm.allowNonAppliedPatches to pnpm.allowUnusedPatches. The old name is still supported but it would print a deprecation warning message.
Add pnpm.ignorePatchFailures to manage whether pnpm would ignore patch application failures.

If ignorePatchFailures is not set, pnpm would throw an error when patches with exact versions or version ranges fail to apply, and it would ignore failures from name-only patches.

If ignorePatchFailures is explicitly set to false, pnpm would throw an error when any type of patch fails to apply.

If ignorePatchFailures is explicitly set to true, pnpm would print a warning when any type of patch fails to apply.

Patch Changes

Remove dependency paths from audit output to prevent out-of-memory errors #9280.

pnpm/action-setup (pnpm/action-setup)

`v4.1.0`

Compare Source

Add support for package.yaml #156.

facebook/react (react)

`v19.1.0`

Compare Source

`v19.0.0`

Compare Source

Below is a list of all new features, APIs, deprecations, and breaking changes. Read React 19 release post and React 19 upgrade guide for more information.

Note: To help make the upgrade to React 19 easier, we’ve published a [email protected] release that is identical to 18.2 but adds warnings for deprecated APIs and other changes that are needed for React 19. We recommend upgrading to React 18.3.1 first to help identify any issues before upgrading to React 19.

New Features

React

Actions: startTransition can now accept async functions. Functions passed to startTransition are called “Actions”. A given Transition can include one or more Actions which update state in the background and update the UI with one commit. In addition to updating state, Actions can now perform side effects including async requests, and the Action will wait for the work to finish before finishing the Transition. This feature allows Transitions to include side effects like fetch() in the pending state, and provides support for error handling, and optimistic updates.
useActionState: is a new hook to order Actions inside of a Transition with access to the state of the action, and the pending state. It accepts a reducer that can call Actions, and the initial state used for first render. It also accepts an optional string that is used if the action is passed to a form action prop to support progressive enhancement in forms.
useOptimistic: is a new hook to update state while a Transition is in progress. It returns the state, and a set function that can be called inside a transition to “optimistically” update the state to expected final value immediately while the Transition completes in the background. When the transition finishes, the state is updated to the new value.
use: is a new API that allows reading resources in render. In React 19, use accepts a promise or Context. If provided a promise, use will suspend until a value is resolved. use can only be used in render but can be called conditionally.
ref as a prop: Refs can now be used as props, removing the need for forwardRef.
Suspense sibling pre-warming: When a component suspends, React will immediately commit the fallback of the nearest Suspense boundary, without waiting for the entire sibling tree to render. After the fallback commits, React will schedule another render for the suspended siblings to “pre-warm” lazy requests.

React DOM Client

<form> action prop: Form Actions allow you to manage forms automatically and integrate with useFormStatus. When a <form> action succeeds, React will automatically reset the form for uncontrolled components. The form can be reset manually with the new requestFormReset API.
<button> and <input> formAction prop: Actions can be passed to the formAction prop to configure form submission behavior. This allows using different Actions depending on the input.
useFormStatus: is a new hook that provides the status of the parent <form> action, as if the form was a Context provider. The hook returns the values: pending, data, method, and action.
Support for Document Metadata: We’ve added support for rendering document metadata tags in components natively. React will automatically hoist them into the <head> section of the document.
Support for Stylesheets: React 19 will ensure stylesheets are inserted into the <head> on the client before revealing the content of a Suspense boundary that depends on that stylesheet.
Support for async scripts: Async scripts can be rendered anywhere in the component tree and React will handle ordering and deduplication.
Support for preloading resources: React 19 ships with preinit, preload, prefetchDNS, and preconnect APIs to optimize initial page loads by moving discovery of additional resources like fonts out of stylesheet loading. They can also be used to prefetch resources used by an anticipated navigation.

React DOM Server

Added prerender and prerenderToNodeStream APIs for static site generation. They are designed to work with streaming environments like Node.js Streams and Web Streams. Unlike renderToString, they wait for data to load for HTML generation.

React Server Components

RSC features such as directives, server components, and server functions are now stable. This means libraries that ship with Server Components can now target React 19 as a peer dependency with a react-server export condition for use in frameworks that support the Full-stack React Architecture. The underlying APIs used to implement a React Server Components bundler or framework do not follow semver and may break between minors in React 19.x. See docs for how to support React Server Components.

Deprecations

Deprecated: element.ref access: React 19 supports ref as a prop, so we’re deprecating element.ref in favor of element.props.ref. Accessing will result in a warning.
react-test-renderer: In React 19, react-test-renderer logs a deprecation warning and has switched to concurrent rendering for web usage. We recommend migrating your tests to @testing-library/react or @testing-library/react-native

Breaking Changes

React 19 brings in a number of breaking changes, including the removals of long-deprecated APIs. We recommend first upgrading to 18.3.1, where we've added additional deprecation warnings. Check out the upgrade guide for more details and guidance on codemodding.

React

New JSX Transform is now required: We introduced a new JSX transform in 2020 to improve bundle size and use JSX without importing React. I

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), 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.

renovate bot added the dependencies label Dec 2, 2024

renovate bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from 8545337 to 1193e8d Compare December 6, 2024 17:56

renovate bot force-pushed the renovate/all-minor-patch branch from 1193e8d to 8231734 Compare December 9, 2024 12:27

renovate bot changed the title ~~chore(deps): update all non-major dependencies~~ fix(deps): update all non-major dependencies Dec 9, 2024

renovate bot force-pushed the renovate/all-minor-patch branch 10 times, most recently from a65dc4d to 6d849cb Compare December 16, 2024 17:19

renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from b1c76e9 to c1cec9e Compare December 26, 2024 03:24

renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 5ea5a57 to 1389f1d Compare December 27, 2024 00:54

renovate bot force-pushed the renovate/all-minor-patch branch 10 times, most recently from 2b24577 to fdcef1f Compare March 7, 2025 06:37

renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 1581254 to d9e59f5 Compare March 14, 2025 05:55

renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from f356109 to 63ac3b6 Compare March 24, 2025 11:20

renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from f1af6b7 to 8232e67 Compare March 27, 2025 07:40

fix(deps): update all non-major dependencies

c14b06c

renovate bot force-pushed the renovate/all-minor-patch branch from 8232e67 to c14b06c Compare March 28, 2025 23:31

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

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

renovate bot commented Dec 2, 2024 •

edited

Loading

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

Are you sure you want to change the base?

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

Conversation

renovate bot commented Dec 2, 2024 • edited Loading

Release Notes

👓 Spec Compliance

🐛 Bug Fix

💅 Polish

🏠 Internal

🐛 Bug Fix

🏠 Internal

v7.26.8 (2025-02-08)

🏠 Internal

🐛 Bug Fix

Minor Changes

Patch Changes

🌟 Features

🩹 Fixes

🩹 Fixes

🩹 Fixes

🧹 Chores

🩹 Fixes

🌟 Features

🩹 Fixes

Minor Changes

Example with Prettier

Previously

Now

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Highlights

Browser Versions

Highlights

Browser Versions

Test runner

UI updates

Breaking

Browser Versions

Highlights

Browser Versions

Minor Changes

Patch Changes

New Features

React

React DOM Client

React DOM Server

React Server Components

Deprecations

Breaking Changes

React

Configuration

renovate bot commented Dec 2, 2024 •

edited

Loading