Bump the dependencies group across 1 directory with 23 updates

[dependabot]

Bumps the dependencies group with 23 updates in the /frontend directory:

Package	From	To
@mantine/core	7.15.3	7.17.0
@mantine/form	7.15.3	7.17.0
@mantine/hooks	7.15.3	7.17.0
@mantine/modals	7.15.3	7.17.0
@mantine/notifications	7.15.3	7.17.0
@sentry/react	8.48.0	9.2.0
@tanstack/react-query	5.62.16	5.66.9
@tanstack/react-query-devtools	5.62.16	5.66.9
react	18.3.1	19.0.0
@types/react	18.3.18	19.0.10
react-dom	18.3.1	19.0.0
@types/react-dom	18.3.5	19.0.4
@tanstack/eslint-plugin-query	5.62.16	5.66.1
@typescript-eslint/eslint-plugin	8.19.1	8.25.0
@typescript-eslint/parser	8.19.1	8.25.0
eslint	9.17.0	9.21.0
eslint-plugin-prettier	5.2.1	5.2.3
eslint-plugin-react-refresh	0.4.16	0.4.19
lint-staged	15.3.0	15.4.3
prettier	3.4.2	3.5.2
typescript	5.7.2	5.7.3
vite	6.0.11	6.1.1
@rollup/rollup-linux-x64-gnu	4.30.1	4.34.8

Updates @mantine/core from 7.15.3 to 7.17.0

Release notes

Sourced from @​mantine/core's releases.

7.17.0 🌶️

View changelog with demos on mantine.dev website

Last 7.x minor release

This is the last minor release in the 7.x series. The next release will be 8.0 with breaking changes and new features.

You are welcome to review the changelog/code and provide feedback and bug reports in Discord or GitHub discussions:

• Changelog – https://alpha.mantine.dev/changelog/8-0-0/
• Source code – https://github.com/mantinedev/mantine/tree/8.0

How to update your project dependencies to the new alpha version:

• Open your package.json
• Find all @mantine/ packages
• Update version of all @mantine/ packages to 8.0.0-alpha.0
• Install dependencies with your package manager, for example, yarn or npm install

Important notes:

• 8.0 release is scheduled for May 5th. Until then you can influence the included breaking changes by proving feedback using Discord or GitHub discussions.
• Currently most of planned breaking changes are implemented – it is not planned to introduce other significant breaking changes (unless new versions of recharts or tiptap are released before May 5th).
• You can find the updated source code in 8.0 branch on GitHub
• Since the changes to codebase are not that significant compared to previous major releases, it is not planned to deprecate 7.x version as soon as 8.0 is release. 7.17.x patches are planned to be released for some time – if you are not ready to migrate to 8.x, you will still be able to receive bug fixes for 7.x (no new features though).

---

Portal reuseTargetNode prop

Portal component now supports reuseTargetNode prop which allows to reuse the same target node for all instances. This option is more performant than the previous behavior, it is recommended to be enabled. This option will be enabled by default in the 8.0 major release.

To enable reuseTargetNode option in all components that depend on Portal, add the following code to your theme:

import { createTheme, Portal } from '@mantine/core';
export const theme = createTheme({
components: {
Portal: Portal.extend({
defaultProps: {
reuseTargetNode: true,
},
}),
},
});

... (truncated)

Commits

• ef93ceb [release] Version: 7.17.0
• 14d652d [@​mantine/core] Add env prop to MantineProvider
• 46dff2c [@​mantine/core] Popover: Add onDismiss prop support
• 78cb2cc [core] Update Next.js to 15 and React to 19
• 619a7e7 [@​mantine/core] Acnhor: Add underline="not-hover" option support
• 19f2c09 [@​mantine/core] Affix: Add theme spacing values support in position prop
• edf3088 Merge branch 'master' of github.com:mantinedev/mantine into 7.17
• 3f1b824 [release] Version: 7.16.3
• db97288 [@​mantine/core] TextInput: Fix autocomplete for variant prop not working
• 1d119c7 [@​mantine/core] Fix clear button overlaying input content in Autocomplete and...
• Additional commits viewable in compare view

Updates @mantine/form from 7.15.3 to 7.17.0

Release notes

Sourced from @​mantine/form's releases.

7.17.0 🌶️

View changelog with demos on mantine.dev website

Last 7.x minor release

This is the last minor release in the 7.x series. The next release will be 8.0 with breaking changes and new features.

You are welcome to review the changelog/code and provide feedback and bug reports in Discord or GitHub discussions:

• Changelog – https://alpha.mantine.dev/changelog/8-0-0/
• Source code – https://github.com/mantinedev/mantine/tree/8.0

How to update your project dependencies to the new alpha version:

• Open your package.json
• Find all @mantine/ packages
• Update version of all @mantine/ packages to 8.0.0-alpha.0
• Install dependencies with your package manager, for example, yarn or npm install

Important notes:

• 8.0 release is scheduled for May 5th. Until then you can influence the included breaking changes by proving feedback using Discord or GitHub discussions.
• Currently most of planned breaking changes are implemented – it is not planned to introduce other significant breaking changes (unless new versions of recharts or tiptap are released before May 5th).
• You can find the updated source code in 8.0 branch on GitHub
• Since the changes to codebase are not that significant compared to previous major releases, it is not planned to deprecate 7.x version as soon as 8.0 is release. 7.17.x patches are planned to be released for some time – if you are not ready to migrate to 8.x, you will still be able to receive bug fixes for 7.x (no new features though).

---

Portal reuseTargetNode prop

Portal component now supports reuseTargetNode prop which allows to reuse the same target node for all instances. This option is more performant than the previous behavior, it is recommended to be enabled. This option will be enabled by default in the 8.0 major release.

To enable reuseTargetNode option in all components that depend on Portal, add the following code to your theme:

import { createTheme, Portal } from '@mantine/core';
export const theme = createTheme({
components: {
Portal: Portal.extend({
defaultProps: {
reuseTargetNode: true,
},
}),
},
});

... (truncated)

Commits

• ef93ceb [release] Version: 7.17.0
• edf3088 Merge branch 'master' of github.com:mantinedev/mantine into 7.17
• 3f1b824 [release] Version: 7.16.3
• f4f2683 Merge branch 'master' of github.com:mantinedev/mantine into 7.17
• dfdbd65 [release] Version: 7.16.2
• 8be2ce4 Merge branch master into 7.17
• e981065 [release] Version: 7.16.1
• 4edaa61 [@​mantine/form] Fix incorrect values handling in form.resetDirty (#7373)
• a5a3838 Merge branch 'master' of github.com:mantinedev/mantine into 7.17
• e8f7b01 [release] Version: 7.16.0
• Additional commits viewable in compare view

Updates @mantine/hooks from 7.15.3 to 7.17.0

Release notes

Sourced from @​mantine/hooks's releases.

7.17.0 🌶️

View changelog with demos on mantine.dev website

Last 7.x minor release

This is the last minor release in the 7.x series. The next release will be 8.0 with breaking changes and new features.

You are welcome to review the changelog/code and provide feedback and bug reports in Discord or GitHub discussions:

• Changelog – https://alpha.mantine.dev/changelog/8-0-0/
• Source code – https://github.com/mantinedev/mantine/tree/8.0

How to update your project dependencies to the new alpha version:

• Open your package.json
• Find all @mantine/ packages
• Update version of all @mantine/ packages to 8.0.0-alpha.0
• Install dependencies with your package manager, for example, yarn or npm install

Important notes:

• 8.0 release is scheduled for May 5th. Until then you can influence the included breaking changes by proving feedback using Discord or GitHub discussions.
• Currently most of planned breaking changes are implemented – it is not planned to introduce other significant breaking changes (unless new versions of recharts or tiptap are released before May 5th).
• You can find the updated source code in 8.0 branch on GitHub
• Since the changes to codebase are not that significant compared to previous major releases, it is not planned to deprecate 7.x version as soon as 8.0 is release. 7.17.x patches are planned to be released for some time – if you are not ready to migrate to 8.x, you will still be able to receive bug fixes for 7.x (no new features though).

---

Portal reuseTargetNode prop

Portal component now supports reuseTargetNode prop which allows to reuse the same target node for all instances. This option is more performant than the previous behavior, it is recommended to be enabled. This option will be enabled by default in the 8.0 major release.

To enable reuseTargetNode option in all components that depend on Portal, add the following code to your theme:

import { createTheme, Portal } from '@mantine/core';
export const theme = createTheme({
components: {
Portal: Portal.extend({
defaultProps: {
reuseTargetNode: true,
},
}),
},
});

... (truncated)

Commits

• ef93ceb [release] Version: 7.17.0
• 6efa833 [@​mantine/hooks] use-file-dialog: Fix incorrect change event handling
• 422f4fd [@​mantine/hooks] use-file-dialog: Init hook
• 78cb2cc [core] Update Next.js to 15 and React to 19
• 3f1b824 [release] Version: 7.16.3
• dfdbd65 [release] Version: 7.16.2
• bb6f692 [@​mantine/hooks] use-hotkeys: Add better support for non-QUERTY keyboards (#7...
• c2920f1 [@​mantine/hooks] Fix potential dangerous access of ref value in useEffect cle...
• e981065 [release] Version: 7.16.1
• 5866fd5 [@​mantine/hooks] use-in-viewport: Fix tracking being stopped when used with a...
• Additional commits viewable in compare view

Updates @mantine/modals from 7.15.3 to 7.17.0

Release notes

Sourced from @​mantine/modals's releases.

7.17.0 🌶️

View changelog with demos on mantine.dev website

Last 7.x minor release

This is the last minor release in the 7.x series. The next release will be 8.0 with breaking changes and new features.

You are welcome to review the changelog/code and provide feedback and bug reports in Discord or GitHub discussions:

• Changelog – https://alpha.mantine.dev/changelog/8-0-0/
• Source code – https://github.com/mantinedev/mantine/tree/8.0

How to update your project dependencies to the new alpha version:

• Open your package.json
• Find all @mantine/ packages
• Update version of all @mantine/ packages to 8.0.0-alpha.0
• Install dependencies with your package manager, for example, yarn or npm install

Important notes:

• 8.0 release is scheduled for May 5th. Until then you can influence the included breaking changes by proving feedback using Discord or GitHub discussions.
• Currently most of planned breaking changes are implemented – it is not planned to introduce other significant breaking changes (unless new versions of recharts or tiptap are released before May 5th).
• You can find the updated source code in 8.0 branch on GitHub
• Since the changes to codebase are not that significant compared to previous major releases, it is not planned to deprecate 7.x version as soon as 8.0 is release. 7.17.x patches are planned to be released for some time – if you are not ready to migrate to 8.x, you will still be able to receive bug fixes for 7.x (no new features though).

---

Portal reuseTargetNode prop

Portal component now supports reuseTargetNode prop which allows to reuse the same target node for all instances. This option is more performant than the previous behavior, it is recommended to be enabled. This option will be enabled by default in the 8.0 major release.

To enable reuseTargetNode option in all components that depend on Portal, add the following code to your theme:

import { createTheme, Portal } from '@mantine/core';
export const theme = createTheme({
components: {
Portal: Portal.extend({
defaultProps: {
reuseTargetNode: true,
},
}),
},
});

... (truncated)

Commits

• ef93ceb [release] Version: 7.17.0
• 78cb2cc [core] Update Next.js to 15 and React to 19
• edf3088 Merge branch 'master' of github.com:mantinedev/mantine into 7.17
• 3f1b824 [release] Version: 7.16.3
• f4f2683 Merge branch 'master' of github.com:mantinedev/mantine into 7.17
• dfdbd65 [release] Version: 7.16.2
• 8be2ce4 Merge branch master into 7.17
• e981065 [release] Version: 7.16.1
• a5a3838 Merge branch 'master' of github.com:mantinedev/mantine into 7.17
• e8f7b01 [release] Version: 7.16.0
• Additional commits viewable in compare view

Updates @mantine/notifications from 7.15.3 to 7.17.0

Release notes

Sourced from @​mantine/notifications's releases.

7.17.0 🌶️

View changelog with demos on mantine.dev website

Last 7.x minor release

This is the last minor release in the 7.x series. The next release will be 8.0 with breaking changes and new features.

You are welcome to review the changelog/code and provide feedback and bug reports in Discord or GitHub discussions:

• Changelog – https://alpha.mantine.dev/changelog/8-0-0/
• Source code – https://github.com/mantinedev/mantine/tree/8.0

How to update your project dependencies to the new alpha version:

• Open your package.json
• Find all @mantine/ packages
• Update version of all @mantine/ packages to 8.0.0-alpha.0
• Install dependencies with your package manager, for example, yarn or npm install

Important notes:

• 8.0 release is scheduled for May 5th. Until then you can influence the included breaking changes by proving feedback using Discord or GitHub discussions.
• Currently most of planned breaking changes are implemented – it is not planned to introduce other significant breaking changes (unless new versions of recharts or tiptap are released before May 5th).
• You can find the updated source code in 8.0 branch on GitHub
• Since the changes to codebase are not that significant compared to previous major releases, it is not planned to deprecate 7.x version as soon as 8.0 is release. 7.17.x patches are planned to be released for some time – if you are not ready to migrate to 8.x, you will still be able to receive bug fixes for 7.x (no new features though).

---

Portal reuseTargetNode prop

Portal component now supports reuseTargetNode prop which allows to reuse the same target node for all instances. This option is more performant than the previous behavior, it is recommended to be enabled. This option will be enabled by default in the 8.0 major release.

To enable reuseTargetNode option in all components that depend on Portal, add the following code to your theme:

import { createTheme, Portal } from '@mantine/core';
export const theme = createTheme({
components: {
Portal: Portal.extend({
defaultProps: {
reuseTargetNode: true,
},
}),
},
});

... (truncated)

Commits

• ef93ceb [release] Version: 7.17.0
• 78cb2cc [core] Update Next.js to 15 and React to 19
• 3f1b824 [release] Version: 7.16.3
• dfdbd65 [release] Version: 7.16.2
• e981065 [release] Version: 7.16.1
• e8f7b01 [release] Version: 7.16.0
• See full diff in compare view

Updates @sentry/react from 8.48.0 to 9.2.0

Release notes

Sourced from @​sentry/react's releases.

9.2.0

Important Changes

• feat(node): Support Express v5 (#15380)

This release adds full tracing support for Express v5, and improves tracing support for Nest.js 11 (which uses Express v5) in the Nest.js SDK.

• feat(sveltekit): Add Support for Cloudflare (#14672)

This release adds support for deploying SvelteKit applications to Cloudflare Pages. A docs update with updated instructions will follow shortly. Until then, you can give this a try by setting up the SvelteKit SDK as usual and then following the instructions outlined in the PR.

Thank you @​SG60 for contributing this feature!

Other Changes

• feat(core): Add addLink(s) to Sentry span (#15452)
• feat(core): Add links to span options (#15453)
• feat(deps): Bump @​sentry/webpack-plugin from 2.22.7 to 3.1.2 (#15328)
• feat(feedback): Disable Feedback submit & cancel buttons while submitting (#15408)
• feat(nextjs): Add experimental flag to not strip origin information from different origin stack frames (#15418)
• feat(nuxt): Add enableNitroErrorHandler to server options (#15444)
• feat(opentelemetry): Add addLink(s) to span (#15387)
• feat(opentelemetry): Add links to span options (#15403)
• feat(replay): Expose rrweb recordCrossOriginIframes under _experiments (#14916)
• fix(browser): Ensure that performance.measure spans have a positive duration (#15415)
• fix(bun): Includes correct sdk metadata (#15459)
• fix(core): Add Google gmo error to Inbound Filters (#15432)
• fix(core): Ensure http.client span descriptions don't contain query params or fragments (#15404)
• fix(core): Filter out unactionable Facebook Mobile browser error (#15430)
• fix(nestjs): Pin dependency on @opentelemetry/instrumentation (#15419)
• fix(nuxt): Only use filename with file extension from command (#15445)
• fix(nuxt): Use SentryNuxtServerOptions type for server init (#15441)
• fix(sveltekit): Avoid loading vite config to determine source maps setting (#15440)
• ref(profiling-node): Bump chunk interval to 60s (#15361)

Work in this release was contributed by @​6farer, @​dgavranic and @​SG60. Thank you for your contributions!

Bundle size 📦

Path	Size
@​sentry/browser	23.05 KB
@​sentry/browser - with treeshaking flags	22.84 KB
@​sentry/browser (incl. Tracing)	36.13 KB
@​sentry/browser (incl. Tracing, Replay)	73.14 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags	66.6 KB
@​sentry/browser (incl. Tracing, Replay with Canvas)	77.39 KB
@​sentry/browser (incl. Tracing, Replay, Feedback)	90.34 KB

... (truncated)

Changelog

Sourced from @​sentry/react's changelog.

9.2.0

Important Changes

• feat(node): Support Express v5 (#15380)

This release adds full tracing support for Express v5, and improves tracing support for Nest.js 11 (which uses Express v5) in the Nest.js SDK.

• feat(sveltekit): Add Support for Cloudflare (#14672)

This release adds support for deploying SvelteKit applications to Cloudflare Pages. A docs update with updated instructions will follow shortly. Until then, you can give this a try by setting up the SvelteKit SDK as usual and then following the instructions outlined in the PR.

Thank you @​SG60 for contributing this feature!

Other Changes

• feat(core): Add addLink(s) to Sentry span (#15452)
• feat(core): Add links to span options (#15453)
• feat(deps): Bump @​sentry/webpack-plugin from 2.22.7 to 3.1.2 (#15328)
• feat(feedback): Disable Feedback submit & cancel buttons while submitting (#15408)
• feat(nextjs): Add experimental flag to not strip origin information from different origin stack frames (#15418)
• feat(nuxt): Add enableNitroErrorHandler to server options (#15444)
• feat(opentelemetry): Add addLink(s) to span (#15387)
• feat(opentelemetry): Add links to span options (#15403)
• feat(replay): Expose rrweb recordCrossOriginIframes under _experiments (#14916)
• fix(browser): Ensure that performance.measure spans have a positive duration (#15415)
• fix(bun): Includes correct sdk metadata (#15459)
• fix(core): Add Google gmo error to Inbound Filters (#15432)
• fix(core): Ensure http.client span descriptions don't contain query params or fragments (#15404)
• fix(core): Filter out unactionable Facebook Mobile browser error (#15430)
• fix(nestjs): Pin dependency on @opentelemetry/instrumentation (#15419)
• fix(nuxt): Only use filename with file extension from command (#15445)
• fix(nuxt): Use SentryNuxtServerOptions type for server init (#15441)
• fix(sveltekit): Avoid loading vite config to determine source maps setting (#15440)
• ref(profiling-node): Bump chunk interval to 60s (#15361)

Work in this release was contributed by @​6farer, @​dgavranic and @​SG60. Thank you for your contributions!

9.1.0

• feat(browser): Add graphqlClientIntegration (#13783)
• feat(core): Allow for nested trpc context (#15379)
• feat(core): Create types and utilities for span links (#15375)
• feat(deps): bump @​opentelemetry/instrumentation-pg from 0.50.0 to 0.51.0 (#15273)
• feat(node): Extract Sentry-specific node-fetch instrumentation (#15231)
• feat(vue): Support Pinia v3 (#15383)
• fix(sveltekit): Avoid request body double read errors (#15368)
• fix(sveltekit): Avoid top-level vite import (#15371)

... (truncated)

Commits

• 995811f release: 9.2.0
• e730bc2 Merge pull request #15454 from getsentry/prepare-release/9.2.0
• 12425e2 start CI please
• 48065f8 meta: Update changelog for 9.2.0
• 14667ee feat(core): Add links to span options (#15453)
• 63ea300 feat(core): Add addLink(s) to Sentry span (#15452)
• bac7387 feat(nextjs): Add experimental flag to not strip origin information from diff...
• 08569e6 Revert "test(node): Add pg-native integration tests" (#15464)
• 8f9f42c feat(sveltekit): Add Support for Cloudflare (#14672)
• e01a428 test(node): Add pg-native integration tests (#15206)
• Additional commits viewable in compare view

Updates @tanstack/react-query from 5.62.16 to 5.66.9

Release notes

Sourced from @​tanstack/react-query's releases.

v5.66.9

Version 5.66.9 - 2/21/25, 1:19 PM

Changes

Fix

• types: prevent type errors and improve inference for dynamic queries on useQueries and useSuspenseQueries (#8624) (f63ba16) by Yoomin Kang

Packages

• @​tanstack/react-query@​5.66.9
• @​tanstack/solid-query@​5.66.9
• @​tanstack/solid-query-devtools@​5.66.9
• @​tanstack/solid-query-persist-client@​5.66.9
• @​tanstack/svelte-query@​5.66.9
• @​tanstack/vue-query@​5.66.9
• @​tanstack/angular-query-experimental@​5.66.9
• @​tanstack/react-query-devtools@​5.66.9
• @​tanstack/react-query-persist-client@​5.66.9
• @​tanstack/react-query-next-experimental@​5.66.9
• @​tanstack/svelte-query-devtools@​5.66.9
• @​tanstack/svelte-query-persist-client@​5.66.9
• @​tanstack/vue-query-devtools@​5.66.9
• @​tanstack/angular-query-devtools-experimental@​5.66.9

v5.66.8

Version 5.66.8 - 2/20/25, 1:11 PM

Changes

Fix

• react-query: fix inferring data as | undefined when using initialData without queryFn (#8674) (9ac54b1) by Yoomin Kang

Docs

• angular-query: Add Optimistic Updates Example for Angular (#8439) (d07a3db) by @​MatanShushan

Packages

• @​tanstack/react-query@​5.66.8
• @​tanstack/react-query-devtools@​5.66.8
• @​tanstack/react-query-persist-client@​5.66.8
• @​tanstack/react-query-next-experimental@​5.66.8

v5.66.7

Version 5.66.7 - 2/18/25, 2:00 PM

Changes

... (truncated)

Commits

• e474f73 release: v5.66.9
• f63ba16 fix(types): prevent type errors and improve inference for dynamic queries on ...
• a4db9ed release: v5.66.8
• 9ac54b1 fix(react-query): fix inferring data as | undefined when using initialData wi...
• c1ea870 release: v5.66.7
• caf7bde refactor: Simplify useQueries (#8661)
• 470ecb6 release: v5.66.6
• 56183f0 fix(react-query): make error to be shown when using queryOptions with initial...
• 044acae release: v5.66.5
• 9a7bfd9 fix(react-query): fix queryOptions with initialData to work on useSuspenseQue...
• Additional commits viewable in compare view

Updates @tanstack/react-query-devtools from 5.62.16 to 5.66.9

Release notes

Sourced from @​tanstack/react-query-devtools's releases.

v5.66.9

Version 5.66.9 - 2/21/25, 1:19 PM

Changes

Fix

• types: prevent type errors and improve inference for dynamic queries on useQueries and useSuspenseQueries (#8624) (f63ba16) by Yoomin Kang

Packages

• @​tanstack/react-query@​5.66.9
• @​tanstack/solid-query@​5.66.9
• @​tanstack/solid-query-devtools@​5.66.9
• @​tanstack/solid-query-persist-client@​5.66.9
• @​tanstack/svelte-query@​5.66.9
• @​tanstack/vue-query@​5.66.9
• @​tanstack/angular-query-experimental@​5.66.9
• @​tanstack/react-query-devtools@​5.66.9
• @​tanstack/react-query-persist-client@​5.66.9
• @​tanstack/react-query-next-experimental@​5.66.9
• @​tanstack/svelte-query-devtools@​5.66.9
• @​tanstack/svelte-query-persist-client@​5.66.9
• @​tanstack/vue-query-devtools@​5.66.9
• @​tanstack/angular-query-devtools-experimental@​5.66.9

v5.66.8

Version 5.66.8 - 2/20/25, 1:11 PM

Changes

Fix

• react-query: fix inferring data as | undefined when using initialData without queryFn (#8674) (9ac54b1) by Yoomin Kang

Docs

• angular-query: Add Optimistic Updates Example for Angular (#8439) (d07a3db) by @​MatanShushan

Packages

• @​tanstack/react-query@​5.66.8
• @​tanstack/react-query-devtools@​5.66.8
• @​tanstack/react-query-persist-client@​5.66.8
• @​tanstack/react-query-next-experimental@​5.66.8

v5.66.7

Version 5.66.7 - 2/18/25, 2:00 PM

Changes

... (truncated)

Commits

• e474f73 release: v5.66.9
• a4db9ed release: v5.66.8
• c1ea870 release: v5.66.7
• 470ecb6 release: v5.66.6
• 044acae release: v5.66.5
• 0588a46 release: v5.66.4
• 56c24f9 fix(devtools): force LTR direction for DevTools panel (#8656)
• accccf9 release: v5.66.3
• ce7e31e release: v5.66.2
• ebe996d release: v5.66.0
• Additional commits viewable in compare view

Updates react from 18.3.1 to 19.0.0

Release notes

Sourced from react's releases.

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 [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 @​testinglibrary.com/docs/react-testing-library/intro/) or @​testingesting-library.com/docs/react-native-testing-library/intro)

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. In React 19, we’re adding additional improvements like using ref as a prop and JSX speed improvements that require the new transform.
• Errors in render are not re-thrown: Errors that are not caught by an Error Boundary are now reported to window.reportError. Errors that are caught by an Error Boundary are reported to console.error. We’ve introduced onUncaughtError and onCaughtError methods to createRoot and hydrateRoot to customize this error handling.
• Removed: propTypes: Using propTypes will now be silently ignored. If required, we recommend migrating to TypeScript or another type-checking solution.
• Removed: defaultProps for functions: ES6 default parameters can be used in place. Class components continue to support defaultProps since there is no ES6 alternative.
• Removed: contextTypes and getChildContext: Legacy Context for class components has been removed in favor of the contextType API.

... (truncated)

Changelog

Sourced from react's changelog.

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 [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...

  Description has been truncated

[dependabot]

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