chore(deps): bump the production group across 1 directory with 27 updates

[dependabot]

Bumps the production group with 27 updates in the / directory:

Package	From	To
@hookform/resolvers	3.1.0	3.6.0
@sentry/nextjs	7.53.1	8.12.0
@tanstack/react-query	4.29.5	5.48.0
axios	1.4.0	1.7.2
classnames	2.3.2	2.5.1
jwt-decode	3.1.2	4.0.0
next-i18next	12.1.0	15.3.0
react	18.2.0	18.3.1
@types/react	18.0.28	18.3.3
react-dom	18.2.0	18.3.1
@types/react-dom	18.2.4	18.3.0
react-error-boundary	3.1.4	4.0.13
react-hook-form	7.43.9	7.52.0
yup	1.2.0	1.4.0
@typescript-eslint/eslint-plugin	6.7.5	7.14.1
@typescript-eslint/parser	6.7.5	7.14.1
eslint	8.51.0	9.5.0
eslint-config-next	13.5.4	14.2.4
eslint-config-prettier	9.0.0	9.1.0
eslint-plugin-no-relative-import-paths	1.5.3	1.5.4
eslint-plugin-prettier	5.0.1	5.1.3
eslint-plugin-unused-imports	3.0.0	4.0.0
prettier	3.0.3	3.3.2
prettier-plugin-tailwindcss	0.5.6	0.6.5
@emotion/react	11.11.0	11.11.4
@headlessui/react	1.7.14	2.1.0
react-router-dom	6.11.1	6.24.0

Updates @hookform/resolvers from 3.1.0 to 3.6.0

Release notes

Sourced from @​hookform/resolvers's releases.

v3.6.0

3.6.0 (2024-06-06)

Features

• upgrade and migrate Valibot to v0.31.0 (#688) (bdd5ef5)

v3.5.0

3.5.0 (2024-06-04)

Features

• migrate arktype resolver to v2 (#686) (c53864f)

v3.4.2

3.4.2 (2024-05-20)

Bug Fixes

• move back to in-build set and remove lodash.set (#685) (5754c47)

v3.4.1

3.4.1 (2024-05-20)

Bug Fixes

• migrate set to lodash.set package (#684) (bdc1f1f)

v3.4.0

3.4.0 (2024-05-15)

Features

• effect-ts resolver (#676) (9ba2f89)

v3.3.4

3.3.4 (2024-01-04)

Bug Fixes

• error handling for array errors with root error (1bfc6ab)

v3.3.3

3.3.3 (2023-12-26)

... (truncated)

Commits

• bdd5ef5 feat: upgrade and migrate Valibot to v0.31.0 (#688)
• c53864f feat: migrate arktype resolver to v2 (#686)
• 767184d chore: remove lodash.set dep
• 5754c47 fix: move back to in-build set and remove lodash.set (#685)
• bdc1f1f fix: migrate set to lodash.set package (#684)
• 9098f59 Update effect-ts README.md (#682)
• 79700b0 Update main.yml (#681)
• 9f5576c Update node version (#680)
• 9408874 Update main.yml (#679)
• ed5457a chore: update main.yml (#678)
• Additional commits viewable in compare view

Updates @sentry/nextjs from 7.53.1 to 8.12.0

Release notes

Sourced from @​sentry/nextjs's releases.

8.12.0

Important Changes

• feat(solid): Remove need to pass router hooks to solid integration (breaking)

This release introduces breaking changes to the @sentry/solid package (which is currently out in alpha).

We've made it easier to get started with the solid router integration by removing the need to pass use* hooks explicitly to solidRouterBrowserTracingIntegration. Import solidRouterBrowserTracingIntegration from @sentry/solid/solidrouter and add it to Sentry.init

import * as Sentry from '@sentry/solid';
import { solidRouterBrowserTracingIntegration, withSentryRouterRouting } from '@sentry/solid/solidrouter';
import { Router } from '@solidjs/router';
Sentry.init({
dsn: 'PUBLIC_DSN',
integrations: [solidRouterBrowserTracingIntegration()],
tracesSampleRate: 1.0, //  Capture 100% of the transactions
});
const SentryRouter = withSentryRouterRouting(Router);

• feat(core): Return client from init method (#12585)

Sentry.init() now returns a client directly, so you don't need to explicitly call getClient() anymore:

const client = Sentry.init();

• feat(nextjs): Add deleteSourcemapsAfterUpload option (#12457)

This adds an easy way to delete sourcemaps immediately after uploading them:

module.exports = withSentryConfig(nextConfig, {
  sourcemaps: {
    deleteSourcemapsAfterUpload: true,
  },
});

• feat(node): Allow to configure maxSpanWaitDuration (#12610)

Adds configuration option for the max. duration in seconds that the SDK will wait for parent spans to be finished before discarding a span. The SDK will automatically clean up spans that have no finished parent after this duration. This is necessary to prevent memory leaks in case of parent spans that are never finished or otherwise dropped/missing. However,

... (truncated)

Changelog

Sourced from @​sentry/nextjs's changelog.

8.12.0

Important Changes

• feat(solid): Remove need to pass router hooks to solid integration (breaking)

This release introduces breaking changes to the @sentry/solid package (which is currently out in alpha).

We've made it easier to get started with the solid router integration by removing the need to pass use* hooks explicitly to solidRouterBrowserTracingIntegration. Import solidRouterBrowserTracingIntegration from @sentry/solid/solidrouter and add it to Sentry.init

import * as Sentry from '@sentry/solid';
import { solidRouterBrowserTracingIntegration, withSentryRouterRouting } from '@sentry/solid/solidrouter';
import { Router } from '@solidjs/router';
Sentry.init({
dsn: 'PUBLIC_DSN',
integrations: [solidRouterBrowserTracingIntegration()],
tracesSampleRate: 1.0, //  Capture 100% of the transactions
});
const SentryRouter = withSentryRouterRouting(Router);

• feat(core): Return client from init method (#12585)

Sentry.init() now returns a client directly, so you don't need to explicitly call getClient() anymore:

const client = Sentry.init();

• feat(nextjs): Add deleteSourcemapsAfterUpload option (#12457)

This adds an easy way to delete sourcemaps immediately after uploading them:

module.exports = withSentryConfig(nextConfig, {
  sourcemaps: {
    deleteSourcemapsAfterUpload: true,
  },
});

• feat(node): Allow to configure maxSpanWaitDuration (#12610)

Adds configuration option for the max. duration in seconds that the SDK will wait for parent spans to be finished before discarding a span. The SDK will automatically clean up spans that have no finished parent after this duration. This is

... (truncated)

Commits

• a38ac88 release: 8.12.0
• a5cd091 Merge pull request #12637 from getsentry/prepare-release/8.12.0
• 944e1ea meta(changelog): Remove non user facing change
• bb85a02 Merge branch 'master' into prepare-release/8.12.0
• 12072b8 meta(changelog): Update changelog for 8.12.0
• dd4a7d7 feat(solid): Remove need to pass router hooks to solid integration (#12617)
• c49c9f3 fix(feedback): Inject preact from feedbackModal into feedbackScreenshot integ...
• 70e942d fix(build) upgrade deprecated runners (#12624)
• b23171b docs: Update slack issue-feed channel for triaging docs (#12618)
• 8b8febb feat(node): Allow to configure maxSpanWaitDuration (#12610)
• Additional commits viewable in compare view

Updates @tanstack/react-query from 4.29.5 to 5.48.0

Release notes

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

v5.48.0

Version 5.48.0 - 6/25/24, 2:14 PM

Changes

Feat

• core: Add possibility to pass a callback to enabled. (#7566) (31b9ab49) by John

Packages

• @​tanstack/query-core@​5.48.0
• @​tanstack/query-broadcast-client-experimental@​5.48.0
• @​tanstack/query-persist-client-core@​5.48.0
• @​tanstack/query-sync-storage-persister@​5.48.0
• @​tanstack/react-query@​5.48.0
• @​tanstack/react-query-devtools@​5.48.0
• @​tanstack/react-query-persist-client@​5.48.0
• @​tanstack/react-query-next-experimental@​5.48.0
• @​tanstack/solid-query@​5.48.0
• @​tanstack/solid-query-devtools@​5.48.0
• @​tanstack/solid-query-persist-client@​5.48.0
• @​tanstack/svelte-query@​5.48.0
• @​tanstack/svelte-query-devtools@​5.48.0
• @​tanstack/svelte-query-persist-client@​5.48.0
• @​tanstack/vue-query@​5.48.0
• @​tanstack/vue-query-devtools@​5.48.0
• @​tanstack/angular-query-experimental@​5.48.0
• @​tanstack/query-async-storage-persister@​5.48.0
• @​tanstack/angular-query-devtools-experimental@​5.48.0

v5.47.0

Version 5.47.0 - 6/25/24, 12:27 PM

Changes

Feat

• react-query: usePrefetchQuery (#7582) (fbfe9409) by Dominik Dorfmeister

Chore

• Update typescript-eslint to v7 (#7610) (32bce35a) by Lachlan Collins

Ci

• Prevent uploading coverage files found in Nx cache (#7619) (63552449) by Lachlan Collins
• Add tests for TS 4.7, 4.8, 4.9 (#7618) (15e42ba4) by Lachlan Collins
• Add TS version tests (#7605) (8253a80b) by Lachlan Collins

... (truncated)

Commits

• 09382a4 release: v5.48.0
• 461f3af release: v5.47.0
• fbfe940 feat(react-query): usePrefetchQuery (#7582)
• 15e42ba ci: Add tests for TS 4.7, 4.8, 4.9 (#7618)
• 8253a80 ci: Add TS version tests (#7605)
• 80a0322 release: v5.45.1
• 77a7b28 refactor(react-query): improve type inference for useSuspenseQueries with ski...
• ac8f48a release: v5.45.0
• b157fe4 release: v5.44.0
• a300d48 release: v5.40.1
• Additional commits viewable in compare view

Updates axios from 1.4.0 to 1.7.2

Release notes

Sourced from axios's releases.

Release v1.7.2

Release notes:

Bug Fixes

• fetch: enhance fetch API detection; (#6413) (4f79aef)

Contributors to this release

• Dmitriy Mozgovoy

Release v1.7.1

Release notes:

Bug Fixes

• fetch: fixed ReferenceError issue when TextEncoder is not available in the environment; (#6410) (733f15f)

Contributors to this release

• Dmitriy Mozgovoy

Release v1.7.0

Release notes:

Features

• adapter: add fetch adapter; (#6371) (a3ff99b)

Bug Fixes

• core/axios: handle un-writable error stack (#6362) (81e0455)

Contributors to this release

• Dmitriy Mozgovoy
• Jay
• Alexandre ABRIOUX

Release v1.7.0-beta.2

Release notes:

Bug Fixes

• fetch: capitalize HTTP method names; (#6395) (ad3174a)
• fetch: fix & optimize progress capturing for cases when the request data has a nullish value or zero data length (#6400) (95a3e8e)
• fetch: fix headers getting from a stream response; (#6401) (870e0a7)

Contributors to this release

• Dmitriy Mozgovoy

Release v1.7.0-beta.1

Release notes:

... (truncated)

Changelog

Sourced from axios's changelog.

1.7.2 (2024-05-21)

Bug Fixes

• fetch: enhance fetch API detection; (#6413) (4f79aef)

Contributors to this release

• Dmitriy Mozgovoy

1.7.1 (2024-05-20)

Bug Fixes

• fetch: fixed ReferenceError issue when TextEncoder is not available in the environment; (#6410) (733f15f)

Contributors to this release

• Dmitriy Mozgovoy

1.7.0 (2024-05-19)

Features

• adapter: add fetch adapter; (#6371) (a3ff99b)

Bug Fixes

• core/axios: handle un-writable error stack (#6362) (81e0455)

Contributors to this release

• Dmitriy Mozgovoy
• Jay
• Alexandre ABRIOUX

1.7.0-beta.2 (2024-05-19)

Bug Fixes

• fetch: capitalize HTTP method names; (#6395) (ad3174a)
• fetch: fix & optimize progress capturing for cases when the request data has a nullish value or zero data length (#6400) (95a3e8e)
• fetch: fix headers getting from a stream response; (#6401) (870e0a7)

Contributors to this release

... (truncated)

Commits

• 0e4f9fa chore(release): v1.7.2 (#6414)
• 4f79aef fix(fetch): enhance fetch API detection; (#6413)
• 67d1373 chore(release): v1.7.1 (#6411)
• 733f15f fix(fetch): fixed ReferenceError issue when TextEncoder is not available in t...
• 3041c61 [Release] v1.7.0 (#6408)
• 18b13cb chore(docs): add fetch adapter docs; (#6407)
• e62099b fix(fetch): fixed a possible memory leak in the AbortController for the strea...
• b49aa8e chore(release): v1.7.0-beta.2 (#6403)
• d57f03a chore(ci): bump create-pull-request version to fix a bug; (#6405)
• 097b0d1 chore(ci): add tag resolution for npm releases based on package version; (#6404)
• Additional commits viewable in compare view

Updates classnames from 2.3.2 to 2.5.1

Changelog

Sourced from classnames's changelog.

v2.5.1 / 2023-12-29

• Remove workspaces field from package (#350)

v2.5.0 / 2023-12-27

• Restore ability to pass a TypeScript interface (#341)
• Add exports field to package (#342)

v2.4.0 / 2023-12-26

• Use string concatenation to increase performance thanks Jon Koops (#336)

v2.3.3 / 2023-12-21

• Fix default export, thanks Remco Haszing (#301)
• Fix types for read-only arrays, thanks Ben Thompson (#307)
• Replace README examples with functional-style components, thanks JoeDGit (#303)

Commits

• 2e36832 Prepare for release of version 2.5.1 (#351)
• 9331401 Remove benchmarks from workspace (#350)
• ff6dd1e Bump to the latest version (#347)
• 942db49 Add GitHub provenance for publishing (#345)
• 28ea73f Prepare for release of version 2.5.0 (#344)
• dfeb7f3 Fix URL for GIT repository in package (#343)
• 8a840ea Add exports field to package (#342)
• ea8e839 Restore ability to pass TypeScript interface (#341)
• 930c748 Bump classnames to the latest version (#340)
• d2d10f5 Bump tsd from 0.30.0 to 0.30.1 (#339)
• Additional commits viewable in compare view

Updates jwt-decode from 3.1.2 to 4.0.0

Release notes

Sourced from jwt-decode's releases.

v4.0.0

A new version of the library, including a couple of improvements:

• No longer include a polyfill for atob, as this is supported in all major browsers (and node environments > 14).
• Compile to ES2017, dropping support for anything that does not support ES2017 (which should be very limited according to caniuse)
• Use Node's atob when running on node.
• Drop support for Node 14 and 16, add support for Node 20.
• Add support for package.json's exports field, for better CJS/ESM support
• Reorganize build artifacts for better CJS/ESM support (cjs and esm needs to be their own directory with a cjs specific package.json file)
• Drop manual UMD bundle creation in index.standalone.ts, but rely on rollup instead.
• Infer JwtPayload and JwtHeader default types from the header argument by using overloads.

Even though some users might experience breaking changes, mostly because of the exports field, the majority should be able to update without making any changes, assuming the SDK is used in environments with support for atob.

Migration to v4.0.0

The jwtDecode function is now no longer the default export, and is instead provided as a named export. Make sure to update your code in places where you are importing this function:

-import jwtDecodefrom "jwt-decode";
+import { jwtDecode } from "jwt-decode";

v4.0.0-beta.4

Breaking changes

• Raise minimum Node.js version to 18 #209 (jonkoops)

Fixed

• fix default condition should be the last one #199 (frederikprijck)

v4.0.0-beta.3

Breaking changes

• Drop UMD bundle #193 (frederikprijck)

Changed

• Use modern JavaScript syntax #187 (jonkoops)
• Use ESNext as default module system #188 (jonkoops)
• Avoid using any bundlers but use tsc instead #192 (frederikprijck)

v4.0.0-beta.2

Changed

• Avoid using default exports #175 (frederikprijck)
• Make options optional no default function parameter initializer #179 (cristobal)

Fixed

• Ensure types are bundled and correctly linked #174 (jonkoops)

v4.0.0-beta.1

Fixed

• Ensure build is run on prepack #167 (frederikprijck)

... (truncated)

Changelog

Sourced from jwt-decode's changelog.

Version 4.0.0

Full Changelog

A new version of the library, including a couple of improvements:

• No longer include a polyfill for atob, as this is supported in all major browsers (and node environments > 14).
• Compile to ES2017, dropping support for anything that does not support ES2017 (which should be very limited according to caniuse)
• Use Node's atob when running on node.
• Drop support for Node 14 and 16, add support for Node 20.
• Add support for package.json's exports field, for better CJS/ESM support
• Reorganize build artifacts for better CJS/ESM support (cjs and esm needs to be their own directory with a cjs specific package.json file)
• Drop manual UMD bundle creation in index.standalone.ts, but rely on rollup instead.
• Infer JwtPayload and JwtHeader default types from the header argument by using overloads.

Even though some users might experience breaking changes, mostly because of the exports field, the majority should be able to update without making any changes, assuming the SDK is used in environments with support for atob.

Migration to v4.0.0

The jwtDecode function is now no longer the default export, and is instead provided as a named export. Make sure to update your code in places where you are importing this function:

-import jwtDecode from "jwt-decode";
+import { jwtDecode } from "jwt-decode";

Version 4.0.0-beta.4

Full Changelog

Breaking changes

• Raise minimum Node.js version to 18 #209 (jonkoops)

Fixed

• fix default condition should be the last one #199 (frederikprijck)

Version 4.0.0-beta.3

Full Changelog

Breaking changes

• Drop UMD bundle #193 (frederikprijck)

Changed

• Use modern JavaScript syntax #187 (jonkoops)
• Use ESNext as default module system #188 (jonkoops)
• Avoid using any bundlers but use tsc instead #192 (frederikprijck)

Version 4.0.0-beta.2

... (truncated)

Commits

• 3b2d105 Update CHANGELOG.md
• bd50db0 Release v4.0.0 (#232)
• bcfd7da Bump actions/checkout from 3 to 4 (#228)
• 6ec1cba Bump concurrently from 8.2.0 to 8.2.2 (#226)
• 807d123 Bump @​typescript-eslint/eslint-plugin from 6.4.1 to 6.9.0 (#229)
• f68e292 Bump eslint-plugin-import from 2.28.1 to 2.29.0 (#230)
• b2e7489 Bump eslint-import-resolver-typescript from 3.6.0 to 3.6.1 (#225)
• ccb6488 Bump lint-staged from 14.0.1 to 15.0.2 (#231)
• cf3cd4f Bump actions/setup-node from 3 to 4 (#227)
• 0ce8017 pin babel/core to recent version and bump jest
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by auth0-oss, a new releaser for jwt-decode since your current version.

Updates next-i18next from 12.1.0 to 15.3.0

Release notes

Sourced from next-i18next's releases.

v15.3.0

• Only overwrite ns config if it provided #2270

v15.2.0

• add possibility to pass resources directly via config and set localePath to null

v15.1.2

• fix: Install error with react-i18next v14 #2248

v15.1.1

• optimize/fix last change for turbo

v15.1.0

• try to fix for turbo #2222

v15.0.0

• refactor: reuse existing i18next instance #2226 -> If you use client side pages (not lazy loading translations), like described here, make sure you set the partialBundledLanguages option to true, like here.

v14.0.3

• fix: correct namespacesRequired type in serverSideTranslations #2203

v14.0.2

• try to fix namespacesRequired in serverSideTranslations is not type-safe anymore #2201

v14.0.1

• try to fix namespacesRequired in serverSideTranslations is not type-safe anymore #2201

v14.0.0

• requires i18next >= v23.0.1
• requires react-i18next >= v13.0.0

v13.3.0

• using a custom backend on server side should also lazy load the passed namespaces

v13.2.2

• pageProps may be undefined on strange setups #2109"

v13.2.1

• types: fix serverSideTranslations args #2104"

v13.2.0

• types: Update serverSideTranslation args type #2097"

v13.1.6

• fix: allow user provided affixes to be used without providing localeStructure #2100"

v13.1.5

• #2089, more stable impelementation of "feat(server-side): custom default config path #2084"

v13.1.4

... (truncated)

Changelog

Sourced from next-i18next's changelog.

15.3.0

• Only overwrite ns config if it provided #2270

15.2.0

• add possibility to pass resources directly via config and set localePath to null

15.1.2

• fix: Install error with react-i18next v14 #2248

15.1.1

• optimize/fix last change for turbo

15.1.0

• try to fix for turbo #2222

15.0.0

• refactor: reuse existing i18next instance #2226 -> If you use client side pages (not lazy loading translations), like described here, make sure you set the partialBundledLanguages option to true, like here.

14.0.3

• fix: correct namespacesRequired type in serverSideTranslations #2203

14.0.2

• try to fix namespacesRequired in serverSideTranslations is not type-safe anymore #2201

14.0.0

• requires i18next >= v23.0.1
• requires react-i18next >= v13.0.0

Breaking changes

i18next 23.0.0 dropped support for older browsers. From nextjs 13, you can use the transpilePackages to avoid issues.

/** @type {import('next').NextConfig} */
const nextConfig = {
  transpilePackages: ['i18next'],
}
module.exports = nextConfig
</tr></table> 

... (truncated)

Commits

• 5c76bce 15.3.0
• 4a852c4 test simple only
• 0736495 Only overwrite ns config if it provided (#2270)
• d4ee4ff doc(issue-2259): Document react state issue (#2260)
• 205e9a4 15.2.0
• 301bd08 add possibility to pass resources directly via config and set localePath to null
• 5a0fe99 update deps for examples
• ed39a2d 15.1.2
• d2bafce release
• 4aedc32 Allow react i18next v14 (#2249)
• Additional commits viewable in compare view

Updates react from 18.2.0 to 18.3.1

Release notes

Sourced from react's releases.

18.3.1 (April 26, 2024)

• Export act from react f1338f

18.3.0 (April 25, 2024)

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

Changelog

Sourced from react's changelog.

18.3.1 (April 26, 2024)

• Export act from react f1338f

18.3.0 (April 25, 2024)

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

Commits

• f1338f8 Export React.act from 18.3
• d6c42f7 Bump to 18.3.1
• 73bfaa1 Turn on key spread warning in jsx-runtime for everyone (#25697)
• c2a246e Turn on string ref deprecation warning for everybody (not codemoddable) (#25383)
• 2cfb474 Bump version from 18.2 to 18.3
• See full diff in compare view

Maintainer changes

This version was pushed to npm by react-bot, a new releaser for react since your current version.

Updates @types/react from 18.0.28 to 18.3.3

Commits

• See full diff in compare view

Updates react-dom from 18.2.0 to 18.3.1

Release notes

Sourced from react-dom's releases.

18.3.1 (April 26, 2024)

• Export act from react f1338f

18.3.0 (April 25, 2024)

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

Changelog

Sourced from react-dom's changelog.

18.3.1 (April 26, 2024)

• Export act from react f1338f

18.3.0 (April 25, 2024)

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

  Description has been truncated