Bump the dependencies group with 9 updates

[dependabot]

Bumps the dependencies group with 9 updates:

Package	From	To
@chakra-ui/react	2.10.7	3.16.0
@next/mdx	14.2.26	15.3.0
date-fns	3.6.0	4.1.0
framer-motion	11.18.2	12.7.4
isomorphic-dompurify	2.22.0	2.23.0
next	14.2.26	15.3.0
react	18.3.1	19.1.0
@types/react	18.3.20	19.1.2
react-dom	18.3.1	19.1.0

Updates @chakra-ui/react from 2.10.7 to 3.16.0

Release notes

Sourced from @​chakra-ui/react's releases.

@​chakra-ui/react@​3.16.0

Minor Changes

• 529244d Thanks @​segunadebayo! - - Global CSS: Improve text selection contrast

  • System

    • Fix issue where borderEnd shorthand was not working despite borderStart being present
    • Fix issue where system.cva return type was incorrect
    • Soften the focus ring for all color palettes

  • Dialog, Drawer: Fix issue where z-index was not being applied correctly

  • [Beta] createOverlay: Add createOverlay utility for programmatically controlling overlay components (Dialog, Drawer, etc.)

@​chakra-ui/react@​3.15.1

Patch Changes

• e3d7db7 Thanks @​segunadebayo! - - Fix issue where backdrop could overlap positioner when reopened quickly
  • Ensure types are consistent with React 19

@​chakra-ui/react@​3.15.0

Minor Changes

• 2f4ea3b Thanks @​segunadebayo! - - useMediaQuery: Fix type signature to allow skipping the second argument

  • RadioCard: Fix accessibility issue due to html structure

  • Slider

    • Add support for origin: end to align the thumb to the end of the track.
    • Expose thumbSize as CSS variables in the root element. Can be useful for styling the slider.

  • Menu

    • Added onSelect event to the Menu.Item component.
    • Ensure menu items have unique IDs to improve accessibility and HTML validation.

@​chakra-ui/react@​3.14.2

... (truncated)

Changelog

Sourced from @​chakra-ui/react's changelog.

3.16.0

Minor Changes

• 529244d Thanks @​segunadebayo! - - Global CSS: Improve text selection contrast

  • System

    • Fix issue where borderEnd shorthand was not working despite borderStart being present
    • Fix issue where system.cva return type was incorrect
    • Soften the focus ring for all color palettes

  • Dialog, Drawer: Fix issue where z-index was not being applied correctly

  • [Beta] createOverlay: Add createOverlay utility for programmatically controlling overlay components (Dialog, Drawer, etc.)

3.15.1

Patch Changes

• e3d7db7 Thanks @​segunadebayo! - - Fix issue where backdrop could overlap positioner when reopened quickly
  • Ensure types are consistent with React 19

3.15.0

Minor Changes

• 2f4ea3b Thanks @​segunadebayo! - - useMediaQuery: Fix type signature to allow skipping the second argument

  • RadioCard: Fix accessibility issue due to html structure

  • Slider

    • Add support for origin: end to align the thumb to the end of the track.
    • Expose thumbSize as CSS variables in the root element. Can be useful for styling the slider.

  • Menu

    • Added onSelect event to the Menu.Item component.
    • Ensure menu items have unique IDs to improve accessibility and HTML validation.

... (truncated)

Commits

• See full diff in compare view

Updates @next/mdx from 14.2.26 to 15.3.0

Release notes

Sourced from @​next/mdx's releases.

v15.3.0

Core Changes

• [dev-overlay] Customize <select> styling for consistency: #76973
• Upgrade React from 029e8bd6-20250306 to 0ca3deeb-20250311: #76989
• [metadata]: add pinterest meta tag: #76988
• [dev-overlay] ensure stripping overlay bundle in prod build: #76976
• Apply env inlining during generate build mode: #76990
• Turbopack: Implement deploymentId: #76904
• track persistent caching usage: #76996
• [metadata] re-insert icons to head for streamed metadata: #76915
• Upgrade React from 0ca3deeb-20250311 to 6aa8254b-20250312: #77033
• Move static-env imports: #77035
• [dev-overlay] Add size setting to preferences: #77027
• Add config for only generating static env: #77038
• chore(HMR clients): Clean up and share code between app and pages router: #76960
• Add dev warning for cross-origin and stabilize allowedDevOrigins: #77044
• unify allowed origin detection handling: #77053
• Handle hash change in all files for static env: #77058
• [dev-overlay] highlight errored code line for runtime errors: #77078
• NFT: Ignore all of Webpack: #77081
• Add experimental build mode flag for env: #77089
• (feat) support client-side instrumentation: #76916
• Fix JSDoc comment for 'seconds' cache life profile: #77084
• refactor(HMR clients): Encapsulate some of the turbopack state tracking into a shared TurbopackHmr class: #76994
• Slightly improve error handling for unknown server actions: #77135
• Fix output standalone for alternative bundler: #76971
• Add alternate bundler plugin information to next info: #77059
• [metadata] remove the default segement check for metadata rendering: #77119
• [dev-overlay] Fix stacking order of highlighted line: #77189
• Upgrade React from 6aa8254b-20250312 to 5398b711-20250314: #77129
• fix(styled-jsx): Pass useLightningcss option to styled-jsx correctly: #77008
• log the instrumentation-client execution time: #77121
• Turbopack: canary-gate production builds: #77146
• [dev-overlay] remove special handling for missing tag error : #77147
• chore(react-dev-overlay): Remove confusingly underscored variables in useErrorOverlayReducer: #77205
• Update middleware request header: #77201
• Update default allowed origins list: #77212
• Ensure deploymentId is used for CSS preloads: #77210
• chore(HMR clients): Fix a bunch of typescript errors by including the appropriate webpack type declarations: #77207
• Update cache handler interface: #76687
• Turbopack: don't include AMP optimizer in NFT: #77242
• Server actions should not read stale data after calling revalidate*: #76885
• [dev-overlay] Blur fader for scrollable container: #77196
• Make revalidate* work when followed by a redirect in a route handler: #77090
• feat: onNavigate for link: #77209
• fix: pass telemetry plugin rspack tests: #77257
• feat(eslint-plugin): add minimal built-in flat presets: #73873
• [perf] skip loading client manifest for static metadata routes: #77260
• Upgrade React from 5398b711-20250314 to c69a5fc5-20250318: #77249

... (truncated)

Commits

• b2ff049 v15.3.0
• 60bfe64 v15.3.0-canary.46
• f71c4a1 v15.3.0-canary.45
• 4451bae v15.3.0-canary.44
• 87d7d8e v15.3.0-canary.43
• 82ab39f v15.3.0-canary.42
• 8f1409d v15.3.0-canary.41
• 2139369 v15.3.0-canary.40
• 66514a6 v15.3.0-canary.39
• fd5669d v15.3.0-canary.38
• Additional commits viewable in compare view

Updates date-fns from 3.6.0 to 4.1.0

Release notes

Sourced from date-fns's releases.

v4.1.0

This release adds time zone support to format functions (that I somehow missed when working on the feature) and fixes a few bugs.

Make sure also upgrade TZDate to v1.0.2 as it includes a bunch of critical bug fixes.

Fixed

• Fixed internal constructFrom throwing an exception on null arguments. While null isn't allowed, the functions should rather return Invalid Date or NaN in such cases. See #3885.

Added

• Added missing time zone support to format, formatISO, formatISO9075, formatRelative and formatRFC3339. See #3886.

v4.0.0

I have great news! First, ten years after its release, date-fns finally gets first-class time zone support.

Another great news is that there aren't many breaking changes in this release. All of them are type-related and will affect only those explicitly using internal date-fns types. Finally, it has been less than a year since the last major release, which is an improvement over the previous four years between v2 and v3. I plan on keeping the pace and minimizing breaking changes moving forward.

Read more about the release in the announcement blog post.

- Sasha @​kossnocorp

Added

• Added time zones support via @date-fns/tz's TZDate class and tz helper function. See its README for the details about the API.

• All relevant functions now accept the context in option, which allows to specify the time zone to make the calculations in. If the function also returns a date, it will be in the specified time zone:

  import { addDays, startOfDay } from "date-fns";
  import { tz } from "@date-fns/tz";
  startOfDay(addDays(Date.now(), 5, { in: tz("Asia/Singapore") }));
  //=> "2024-09-16T00:00:00.000+08:00"

  In the example, addDays will get the current date and time in Singapore and add 5 days to it. startOfDay will inherit the date type and return the start of the day in Singapore.

Changed

• The function arguments, as well as Interval's start and end, now can be of different types, allowing you to mix UTCDate, TZDate, Date, and other extensions, as well as primitives (strings and numbers).

  The functions will normalize these values, make calculations, and return the result in the same type, preventing any bugs caused by the discrepancy. If passed, the type will be inferred from the context in option or the first encountered argument object type. The Interval's start and end will be considered separately, starting from start.

  In the given example, the result will be in the TZDate as the first argument is a number, and the start takes precedence over the end.

  clamp(Date.now(), {
    start: new TZDate(start, "Asia/Singapore"),
    end: new UTCDate(),

... (truncated)

Changelog

Sourced from date-fns's changelog.

v4.1.0 - 2024-09-17

This release adds time zone support to format functions (that I somehow missed when working on the feature) and fixes a few bugs.

Make sure also upgrade TZDate to v1.0.2 as it includes a bunch of critical bug fixes.

Fixed

• Fixed internal constructFrom throwing an exception on null arguments. While null isn't allowed, the functions should rather return Invalid Date or NaN in such cases. See #3885.

Added

• Added missing time zone support to format, formatISO, formatISO9075, formatRelative and formatRFC3339. See #3886.

v4.0.0 - 2024-09-16

I have great news! First, ten years after its release, date-fns finally gets first-class time zone support.

Another great news is that there aren't many breaking changes in this release. All of them are type-related and will affect only those explicitly using internal date-fns types. Finally, it has been less than a year since the last major release, which is an improvement over the previous four years between v2 and v3. I plan on keeping the pace and minimizing breaking changes moving forward.

Read more about the release in the announcement blog post.

- Sasha @​kossnocorp

Added

• Added time zones support via @date-fns/tz's TZDate class and tz helper function. See its README for the details about the API.

• All relevant functions now accept the context in option, which allows to specify the time zone to make the calculations in. If the function also returns a date, it will be in the specified time zone:

  import { addDays, startOfDay } from "date-fns";
  import { tz } from "@date-fns/tz";
  startOfDay(addDays(Date.now(), 5, { in: tz("Asia/Singapore") }));
  //=> "2024-09-16T00:00:00.000+08:00"

  In the example, addDays will get the current date and time in Singapore and add 5 days to it. startOfDay will inherit the date type and return the start of the day in Singapore.

Changed

• The function arguments, as well as Interval's start and end, now can be of different types, allowing you to mix UTCDate, TZDate, Date, and other extensions, as well as primitives (strings and numbers).

  The functions will normalize these values, make calculations, and return the result in the same type, preventing any bugs caused by the discrepancy. If passed, the type will be inferred from the context in option or the first encountered argument object type. The Interval's start and end will be considered separately, starting from start.

  In the given example, the result will be in the TZDate as the first argument is a number, and the start takes precedence over the end.

  clamp(Date.now(), {

... (truncated)

Commits

• 313b902 Fix v4.1.0 change log entry
• 26cd336 Promote to v4.1.0
• 97b53b9 Cover time zone edge cases
• 59b7563 Add missing time zone support to format, formatISO, formatISO9075, formatRela...
• 0121164 Prevent constructFrom from throwing an error on null
• bd87ef5 Update @​date-fns/docs
• 99b4e67 Prepare v4.0
• 8df1706 Rewrite the time zones doc
• e351977 Promote to v4.0.0-beta.1
• 8523656 Fix scripts/test/types.sh
• Additional commits viewable in compare view

Updates framer-motion from 11.18.2 to 12.7.4

Changelog

Sourced from framer-motion's changelog.

[12.7.4] 2025-04-17

Fixed

• Removed non-deterministic behaviour from AnimatePresence.

[12.7.3] 2025-04-15

Fixed

• Fixing duration for animateView transitions.
• Prevent .commitStyles() on pseudoElement animations.

[12.7.2] 2025-04-14

Fixed

• Adding "sideEffects": false to motion-dom and motion-utils packages.

[12.7.1] 2025-04-14

Fixed

• Skip .commitStyles on psuedoElement animations.

[12.7.0] 2025-04-14

Added

• Private layoutCrossfade allows disabling crossfade of shared layout elements.

[12.6.5] 2025-04-11

Fixed

• Polyfilled sync and cancelSync exports.

[12.6.4] 2025-04-11

Added

• Global injection of WillChangeMotionValue for internal Framer use.

[12.6.3] 2025-04-01

Changed

• Refactored mini animate and animateView to share the same NativeAnimation. Mini animate down to 2.3kb.

Fixed

... (truncated)

Commits

• 2e0e241 v12.7.4
• 2adb8a3 Updating changelog
• 672bb0a Merge pull request #3149 from gnoff/remove-random
• 6ab8045 Merge branch 'main' into remove-random
• 7446d2c Adding force measure
• b9f31f1 Latest
• c226d1a v12.7.3
• 7b7a2b8 Fixing animateView durations
• 522ba09 v12.7.2
• 2697f14 Latest
• Additional commits viewable in compare view

Updates isomorphic-dompurify from 2.22.0 to 2.23.0

Release notes

Sourced from isomorphic-dompurify's releases.

Updated dependencies

Changelog

• Updated dompurify.
• Updated other dependencies.

See the complete changelog for more details.

Release

2.23.0

Commits

• d1c8547 Incremented project version.
• 8bd4815 Updated deps.
• 8841a00 Merge pull request #327 from kkomelin/dependabot/npm_and_yarn/dompurify-3.2.5
• 84b9c03 Bump dompurify from 3.2.4 to 3.2.5
• c62594b Merge pull request #326 from kkomelin/dependabot/npm_and_yarn/vitest-3.1.1
• ea14762 Bump vitest from 3.0.9 to 3.1.1
• fe35b59 Merge pull request #323 from kkomelin/dependabot/npm_and_yarn/vitest-3.0.9
• 91370f3 Bump vitest from 3.0.8 to 3.0.9
• 5e06576 Merge pull request #322 from kkomelin/dependabot/npm_and_yarn/vitest-3.0.8
• 74277b7 Bump vitest from 3.0.7 to 3.0.8
• Additional commits viewable in compare view

Updates next from 14.2.26 to 15.3.0

Release notes

Sourced from next's releases.

v15.3.0

Core Changes

• [dev-overlay] Customize <select> styling for consistency: #76973
• Upgrade React from 029e8bd6-20250306 to 0ca3deeb-20250311: #76989
• [metadata]: add pinterest meta tag: #76988
• [dev-overlay] ensure stripping overlay bundle in prod build: #76976
• Apply env inlining during generate build mode: #76990
• Turbopack: Implement deploymentId: #76904
• track persistent caching usage: #76996
• [metadata] re-insert icons to head for streamed metadata: #76915
• Upgrade React from 0ca3deeb-20250311 to 6aa8254b-20250312: #77033
• Move static-env imports: #77035
• [dev-overlay] Add size setting to preferences: #77027
• Add config for only generating static env: #77038
• chore(HMR clients): Clean up and share code between app and pages router: #76960
• Add dev warning for cross-origin and stabilize allowedDevOrigins: #77044
• unify allowed origin detection handling: #77053
• Handle hash change in all files for static env: #77058
• [dev-overlay] highlight errored code line for runtime errors: #77078
• NFT: Ignore all of Webpack: #77081
• Add experimental build mode flag for env: #77089
• (feat) support client-side instrumentation: #76916
• Fix JSDoc comment for 'seconds' cache life profile: #77084
• refactor(HMR clients): Encapsulate some of the turbopack state tracking into a shared TurbopackHmr class: #76994
• Slightly improve error handling for unknown server actions: #77135
• Fix output standalone for alternative bundler: #76971
• Add alternate bundler plugin information to next info: #77059
• [metadata] remove the default segement check for metadata rendering: #77119
• [dev-overlay] Fix stacking order of highlighted line: #77189
• Upgrade React from 6aa8254b-20250312 to 5398b711-20250314: #77129
• fix(styled-jsx): Pass useLightningcss option to styled-jsx correctly: #77008
• log the instrumentation-client execution time: #77121
• Turbopack: canary-gate production builds: #77146
• [dev-overlay] remove special handling for missing tag error : #77147
• chore(react-dev-overlay): Remove confusingly underscored variables in useErrorOverlayReducer: #77205
• Update middleware request header: #77201
• Update default allowed origins list: #77212
• Ensure deploymentId is used for CSS preloads: #77210
• chore(HMR clients): Fix a bunch of typescript errors by including the appropriate webpack type declarations: #77207
• Update cache handler interface: #76687
• Turbopack: don't include AMP optimizer in NFT: #77242
• Server actions should not read stale data after calling revalidate*: #76885
• [dev-overlay] Blur fader for scrollable container: #77196
• Make revalidate* work when followed by a redirect in a route handler: #77090
• feat: onNavigate for link: #77209
• fix: pass telemetry plugin rspack tests: #77257
• feat(eslint-plugin): add minimal built-in flat presets: #73873
• [perf] skip loading client manifest for static metadata routes: #77260
• Upgrade React from 5398b711-20250314 to c69a5fc5-20250318: #77249

... (truncated)

Commits

• b2ff049 v15.3.0
• 97ad23f IA 2.0: Add "Next Steps" link to /docs landing page (#77981)
• 60bfe64 v15.3.0-canary.46
• 7b483cb Upgrade React from 33661467-20250407 to 3fbfb9ba-20250409 (#77982)
• 664110c Turbopack: read asset entries strongly consistent (#77974)
• 741f6fc Revert standalone extension change for module type (#77978)
• 6d5df0e Update bundler development test manifest (#77959)
• cecfb25 Update bundler production test manifest (#77958)
• c010ecb Revert "docs: revert image 15.3 change until live" (#77977)
• 154267c Turbopack: fix instrumentation asset context name (#77973)
• Additional commits viewable in compare view

Updates react from 18.3.1 to 19.1.0

Release notes

Sourced from react's releases.

19.1.0 (March 28, 2025)

Owner Stack

An Owner Stack is a string representing the components that are directly responsible for rendering a particular component. You can log Owner Stacks when debugging or use Owner Stacks to enhance error overlays or other development tools. Owner Stacks are only available in development builds. Component Stacks in production are unchanged.

• An Owner Stack is a development-only stack trace that helps identify which components are responsible for rendering a particular component. An Owner Stack is distinct from a Component Stacks, which shows the hierarchy of components leading to an error.
• The captureOwnerStack API is only available in development mode and returns a Owner Stack, if available. The API can be used to enhance error overlays or log component relationships when debugging. #29923, #32353, #30306, #32538, #32529, #32538

React

• Enhanced support for Suspense boundaries to be used anywhere, including the client, server, and during hydration. #32069, #32163, #32224, #32252
• Reduced unnecessary client rendering through improved hydration scheduling #31751
• Increased priority of client rendered Suspense boundaries #31776
• Fixed frozen fallback states by rendering unfinished Suspense boundaries on the client. #31620
• Reduced garbage collection pressure by improving Suspense boundary retries. #31667
• Fixed erroneous “Waiting for Paint” log when the passive effect phase was not delayed #31526
• Fixed a regression causing key warnings for flattened positional children in development mode. #32117
• Updated useId to use valid CSS selectors, changing format from :r123: to «r123». #32001
• Added a dev-only warning for null/undefined created in useEffect, useInsertionEffect, and useLayoutEffect. #32355
• Fixed a bug where dev-only methods were exported in production builds. React.act is no longer available in production builds. #32200
• Improved consistency across prod and dev to improve compatibility with Google Closure Complier and bindings #31808
• Improve passive effect scheduling for consistent task yielding. #31785
• Fixed asserts in React Native when passChildrenWhenCloningPersistedNodes is enabled for OffscreenComponent rendering. #32528
• Fixed component name resolution for Portal #32640
• Added support for beforetoggle and toggle events on the dialog element. #32479 #32479

React DOM

• Fixed double warning when the href attribute is an empty string #31783
• Fixed an edge case where getHoistableRoot() didn’t work properly when the container was a Document #32321
• Removed support for using HTML comments (e.g. <!-- -->) as a DOM container. #32250
• Added support for <script> and \<template> tags to be nested within <select> tags. #31837
• Fixed responsive images to be preloaded as HTML instead of headers #32445

use-sync-external-store

• Added exports field to package.json for use-sync-external-store to support various entrypoints. #25231

React Server Components

• Added unstable_prerender, a new experimental API for prerendering React Server Components on the server #31724
• Fixed an issue where streams would hang when receiving new chunks after a global error #31840, #31851
• Fixed an issue where pending chunks were counted twice. #31833
• Added support for streaming in edge environments #31852
• Added support for sending custom error names from a server so that they are available in the client for console replaying. #32116
• Updated the server component wire format to remove IDs for hints and console.log because they have no return value #31671
• Exposed registerServerReference in client builds to handle server references in different environments. #32534
• Added react-server-dom-parcel package which integrates Server Components with the Parcel bundler #31725, #32132, #31799, #32294, #31741

19.0.0 (December 5, 2024)

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 react@18.3 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.

... (truncated)

Changelog

Sourced from react's changelog.

19.1.0 (March 28, 2025)

Owner Stack

An Owner Stack is a string representing the components that are directly responsible for rendering a particular component. You can log Owner Stacks when debugging or use Owner Stacks to enhance error overlays or other development tools. Owner Stacks are only available in development builds. Component Stacks in production are unchanged.

• An Owner Stack is a development-only stack trace that helps identify which components are responsible for rendering a particular component. An Owner Stack is distinct from a Component Stacks, which shows the hierarchy of components leading to an error.
• The captureOwnerStack API is only available in development mode and returns a Owner Stack, if available. The API can be used to enhance error overlays or log component relationships when debugging. #29923, #32353, #30306, #32538, #32529, #32538

React

• Enhanced support for Suspense boundaries to be used anywhere, including the client, server, and during hydration. #32069, #32163, #32224, #32252
• Reduced unnecessary client rendering through improved hydration scheduling #31751
• Increased priority of client rendered Suspense boundaries #31776
• Fixed frozen fallback states by rendering unfinished Suspense boundaries on the client. #31620
• Reduced garbage collection pressure by improving Suspense boundary retries. #31667
• Fixed erroneous “Waiting for Paint” log when the passive effect phase was not delayed #31526
• Fixed a regression causing key warnings for flattened positional children in development mode. #32117
• Updated useId to use valid CSS selectors, changing format from :r123: to «r123». #32001
• Added a dev-only warning for null/undefined created in useEffect, useInsertionEffect, and useLayoutEffect. #32355
• Fixed a bug where dev-only methods were exported in production builds. React.act is no longer available in production builds. #32200
• Improved consistency across prod and dev to improve compatibility with Google Closure Complier and bindings #31808
• Improve passive effect scheduling for consistent task yielding. #31785
• Fixed asserts in React Native when passChildrenWhenCloningPersistedNodes is enabled for OffscreenComponent rendering. #32528
• Fixed component name resolution for Portal #32640
• Added support for beforetoggle and toggle events on the dialog element. #32479 #32479

React DOM

• Fixed double warning when the href attribute is an empty string #31783
• Fixed an edge case where getHoistableRoot() didn’t work properly when the container was a Document #32321
• Removed support for using HTML comments (e.g. <!-- -->) as a DOM container. #32250
• Added support for <script> and \<template> tags to be nested within <select> tags. #31837
• Fixed responsive images to be preloaded as HTML instead of headers #32445

use-sync-external-store

• Added exports field to package.json for use-sync-external-store to support various entrypoints. #25231

React Server Components

• Added unstable_prerender, a new experimental API for prerendering React Server Components on the server #31724
• Fixed an issue where streams would hang when receiving new chunks after a global error #31840, #31851
• Fixed an issue where pending chunks were counted twice. #31833
• Added support for streaming in edge environments #31852
• Added support for sending custom error names from a server so that they are available in the client for console replaying. #32116
• Updated the server component wire format to remove IDs for hints and console.log because they have no return value #31671
• Exposed registerServerReference in client builds to handle server references in different environments. #32534
• Added react-server-dom-parcel package which integrates Server Components with the Parcel bundler #31725, #32132, #31799, #32294, #31741

19.0.0 (December 5, 2024)

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.

... (truncated)

Commits

• 4a9df08 Stop creating Owner Stacks if many have been created recently (#32529)
• b630219 [refactor] move isValidElementType to react-is (#32518)
• 1a19170 [refactor] Add element type for Activity (#32499)
• 6aa8254 Add ref to Fragment (#32465)
• e0fe347 [flags] remove enableOwnerStacks (#32426)
• 70f1d76 [flow] Eliminate usage of global React types in ReactNativeTypes.js (#32330)
• 0d9834c build: add support to the rollup build for building typescript packages (#32393)
• a53da6a Add useSwipeTransition Hook Behind Experimental Flag (#32373)
• 32b0cad Enable owner stacks in Canary builds (#32053)
• ed8b68d Stop exporting dev-only methods in OSS production builds (#32200)
• Additional commits viewable in compare view

Updates @types/react from 18.3.20 to 19.1.2

Commits

• See full diff in compare view

Updates react-dom from 18.3.1 to 19.1.0

Release notes

Sourced from react-dom's releases.

19.1.0 (March 28, 2025)

Owner Stack

An Owner Stack is a string representing the components that are directly responsible for rendering a particular component. You can log Owner Stacks when debugging or use Owner Stacks to enhance error overlays or other development tools. Owner Stacks are only available in development builds. Component Stacks in production are unchanged.

• An Owner Stack is a development-only stack trace that helps identify which components are responsible for rendering a particular component. An Owner Stack is distinct from a Component Stacks, which shows the hierarchy of components leading to an error.
• The captureOwnerStack API is only available in development mode and returns a Owner Stack, if available. The API can be used to enhance error overlays or log component relationships when debugging. #29923, #32353, #30306, #32538, #32529, #32538

React

• Enhanced support for Suspense boundaries to be used anywhere, including the client, server, and during hydration. #32069, #32163, #32224, #32252
• Reduced unnecessary client rendering through improved hydration scheduling #31751
• Increased priority of client rendered Suspense boundaries #31776
• Fixed frozen fallback states by rendering unfinished Suspense boundaries on the client. #31620
• Reduced garbage collection pressure by improving Suspense boundary retries. #31667
• Fixed erroneous “Waiting for Paint” log when the passive effect phase was not delayed #31526
• Fixed a regression causing key warnings for flattened positional children in development mode. #32117
• Updated useId to use valid CSS selectors, changing format from :r123: to «r123». #32001
• Added a dev-only warning for null/undefined created in useEffect, useInsertionEffect, and useLayoutEffect. #32355
• Fixed a bug where dev-only methods we...

  Description has been truncated

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.