[PR #111] [CLOSED] Bump react from 18.3.1 to 19.0.0 #189

New issue

Closed

opened 2026-05-06 12:15:47 +02:00 by BreizhHardware · 0 comments

BreizhHardware commented

2026-05-06 12:15:47 +02:00

Owner

📋 Pull Request Information

Original PR: https://github.com/BreizhHardware/portfolio/pull/111
Author: @dependabot[bot]
Created: 1/20/2025
Status: ❌ Closed

Base: master ← Head: dependabot/npm_and_yarn/react-19.0.0

📝 Commits (1)

041b654 Bump react from 18.3.1 to 19.0.0

📊 Changes

2 files changed (+6 additions, -8 deletions)

View changed files

📝 package-lock.json (+5 -7)
📝 package.json (+1 -1)

📄 Description

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

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

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

... (truncated)

Commits

e137890 [string-refs] cleanup string ref code (#31443)
d1f0472 [string-refs] remove enableLogStringRefsProd flag (#31414)
3dc1e48 Followup: remove dead test code from #30346 (#31415)
07aa494 Remove enableRefAsProp feature flag (#30346)
45804af [flow] Eliminate usage of more than 1-arg React.AbstractComponent in React ...
5636fad [string-refs] log string ref from prod (#31161)
b78a7f2 [rcr] Re-export useMemoCache in top level React namespace (#31139)
4e9540e [Fiber] Log the Render/Commit phases and the gaps in between (#31016)
d4688df [Fiber] Track Event Time, startTransition Time and setState Time (#31008)
15da917 Don't read currentTransition back from internals (#30991)
Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note

Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/BreizhHardware/portfolio/pull/111 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 1/20/2025 **Status:** ❌ Closed **Base:** `master` ← **Head:** `dependabot/npm_and_yarn/react-19.0.0` --- ### 📝 Commits (1) - [`041b654`](https://github.com/BreizhHardware/portfolio/commit/041b6545809329d0a7770ab3a963cfc911ccc9fe) Bump react from 18.3.1 to 19.0.0 ### 📊 Changes **2 files changed** (+6 additions, -8 deletions) <details> <summary>View changed files</summary> 📝 `package-lock.json` (+5 -7) 📝 `package.json` (+1 -1) </details> ### 📄 Description Bumps [react](https://github.com/facebook/react/tree/HEAD/packages/react) from 18.3.1 to 19.0.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/facebook/react/releases">react's releases</a>.</em></p> <blockquote> <h2>19.0.0 (December 5, 2024)</h2> <p>Below is a list of all new features, APIs, deprecations, and breaking changes. Read <a href="https://react.dev/blog/2024/04/25/react-19">React 19 release post</a> and <a href="https://react.dev/blog/2024/04/25/react-19-upgrade-guide">React 19 upgrade guide</a> for more information.</p> <blockquote> <p>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.</p> </blockquote> <h2>New Features</h2> <h3>React</h3> <ul> <li>Actions: <code>startTransition</code> can now accept async functions. Functions passed to <code>startTransition</code> 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 <code>fetch()</code> in the pending state, and provides support for error handling, and optimistic updates.</li> <li><code>useActionState</code>: 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 <code>action</code> prop to support progressive enhancement in forms.</li> <li><code>useOptimistic</code>: 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.</li> <li><code>use</code>: is a new API that allows reading resources in render. In React 19, <code>use</code> accepts a promise or Context. If provided a promise, <code>use</code> will suspend until a value is resolved. <code>use</code> can only be used in render but can be called conditionally.</li> <li><code>ref</code> as a prop: Refs can now be used as props, removing the need for <code>forwardRef</code>.</li> <li><strong>Suspense sibling pre-warming</strong>: 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.</li> </ul> <h3>React DOM Client</h3> <ul> <li><code><form> action</code> prop: Form Actions allow you to manage forms automatically and integrate with <code>useFormStatus</code>. When a <code><form> action</code> succeeds, React will automatically reset the form for uncontrolled components. The form can be reset manually with the new <code>requestFormReset</code> API.</li> <li><code><button> and <input> formAction</code> prop: Actions can be passed to the <code>formAction</code> prop to configure form submission behavior. This allows using different Actions depending on the input.</li> <li><code>useFormStatus</code>: is a new hook that provides the status of the parent <code><form> action</code>, as if the form was a Context provider. The hook returns the values: <code>pending</code>, <code>data</code>, <code>method</code>, and <code>action</code>.</li> <li>Support for Document Metadata: We’ve added support for rendering document metadata tags in components natively. React will automatically hoist them into the <code><head></code> section of the document.</li> <li>Support for Stylesheets: React 19 will ensure stylesheets are inserted into the <code><head></code> on the client before revealing the content of a Suspense boundary that depends on that stylesheet.</li> <li>Support for async scripts: Async scripts can be rendered anywhere in the component tree and React will handle ordering and deduplication.</li> <li>Support for preloading resources: React 19 ships with <code>preinit</code>, <code>preload</code>, <code>prefetchDNS</code>, and <code>preconnect</code> 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.</li> </ul> <h3>React DOM Server</h3> <ul> <li>Added <code>prerender</code> and <code>prerenderToNodeStream</code> APIs for static site generation. They are designed to work with streaming environments like Node.js Streams and Web Streams. Unlike <code>renderToString</code>, they wait for data to load for HTML generation.</li> </ul> <h3>React Server Components</h3> <ul> <li>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 <a href="https://19.react.dev/reference/rsc/server-components">docs</a> for how to support React Server Components.</li> </ul> <h2>Deprecations</h2> <ul> <li>Deprecated: <code>element.ref</code> access: React 19 supports ref as a prop, so we’re deprecating <code>element.ref</code> in favor of <code>element.props.ref</code>. Accessing will result in a warning.</li> <li><code>react-test-renderer</code>: 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 <a href="https://github.com/testinglibrary"><code>@testinglibrary</code></a>.com/docs/react-testing-library/intro/) or <a href="https://github.com/testingesting-library"><code>@testingesting-library</code></a>.com/docs/react-native-testing-library/intro)</li> </ul> <h2>Breaking Changes</h2> <p>React 19 brings in a number of breaking changes, including the removals of long-deprecated APIs. We recommend first upgrading to <code>18.3.1</code>, where we've added additional deprecation warnings. Check out the <a href="https://19.react.dev/blog/2024/04/25/react-19-upgrade-guide">upgrade guide</a> for more details and guidance on codemodding.</p> <h3>React</h3> <ul> <li>New JSX Transform is now required: We introduced <a href="https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html">a new JSX transform</a> 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.</li> <li>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 <code>onUncaughtError</code> and <code>onCaughtError</code> methods to <code>createRoot</code> and <code>hydrateRoot</code> to customize this error handling.</li> <li>Removed: <code>propTypes</code>: Using <code>propTypes</code> will now be silently ignored. If required, we recommend migrating to TypeScript or another type-checking solution.</li> <li>Removed: <code>defaultProps</code> for functions: ES6 default parameters can be used in place. Class components continue to support <code>defaultProps</code> since there is no ES6 alternative.</li> <li>Removed: <code>contextTypes</code> and <code>getChildContext</code>: Legacy Context for class components has been removed in favor of the <code>contextType</code> API.</li> </ul>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/facebook/react/blob/main/CHANGELOG.md">react's changelog</a>.</em></p> <blockquote> <h2>19.0.0 (December 5, 2024)</h2> <p>Below is a list of all new features, APIs, deprecations, and breaking changes. Read <a href="https://react.dev/blog/2024/04/25/react-19">React 19 release post</a> and <a href="https://react.dev/blog/2024/04/25/react-19-upgrade-guide">React 19 upgrade guide</a> for more information.</p> <blockquote> <p>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.</p> </blockquote> <h3>New Features</h3> <h4>React</h4> <ul> <li>Actions: <code>startTransition</code> can now accept async functions. Functions passed to <code>startTransition</code> 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 <code>fetch()</code> in the pending state, and provides support for error handling, and optimistic updates.</li> <li><code>useActionState</code>: 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 <code>action</code> prop to support progressive enhancement in forms.</li> <li><code>useOptimistic</code>: 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.</li> <li><code>use</code>: is a new API that allows reading resources in render. In React 19, <code>use</code> accepts a promise or Context. If provided a promise, <code>use</code> will suspend until a value is resolved. <code>use</code> can only be used in render but can be called conditionally.</li> <li><code>ref</code> as a prop: Refs can now be used as props, removing the need for <code>forwardRef</code>.</li> <li><strong>Suspense sibling pre-warming</strong>: 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.</li> </ul> <h4>React DOM Client</h4> <ul> <li><code><form> action</code> prop: Form Actions allow you to manage forms automatically and integrate with <code>useFormStatus</code>. When a <code><form> action</code> succeeds, React will automatically reset the form for uncontrolled components. The form can be reset manually with the new <code>requestFormReset</code> API.</li> <li><code><button> and <input> formAction</code> prop: Actions can be passed to the <code>formAction</code> prop to configure form submission behavior. This allows using different Actions depending on the input.</li> <li><code>useFormStatus</code>: is a new hook that provides the status of the parent <code><form> action</code>, as if the form was a Context provider. The hook returns the values: <code>pending</code>, <code>data</code>, <code>method</code>, and <code>action</code>.</li> <li>Support for Document Metadata: We’ve added support for rendering document metadata tags in components natively. React will automatically hoist them into the <code><head></code> section of the document.</li> <li>Support for Stylesheets: React 19 will ensure stylesheets are inserted into the <code><head></code> on the client before revealing the content of a Suspense boundary that depends on that stylesheet.</li> <li>Support for async scripts: Async scripts can be rendered anywhere in the component tree and React will handle ordering and deduplication.</li> <li>Support for preloading resources: React 19 ships with <code>preinit</code>, <code>preload</code>, <code>prefetchDNS</code>, and <code>preconnect</code> 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.</li> </ul> <h4>React DOM Server</h4> <ul> <li>Added <code>prerender</code> and <code>prerenderToNodeStream</code> APIs for static site generation. They are designed to work with streaming environments like Node.js Streams and Web Streams. Unlike <code>renderToString</code>, they wait for data to load for HTML generation.</li> </ul> <h4>React Server Components</h4> <ul> <li>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 <a href="https://19.react.dev/reference/rsc/server-components">docs</a> for how to support React Server Components.</li> </ul> <h3>Deprecations</h3> <ul> <li>Deprecated: <code>element.ref</code> access: React 19 supports ref as a prop, so we’re deprecating <code>element.ref</code> in favor of <code>element.props.ref</code>. Accessing will result in a warning.</li> <li><code>react-test-renderer</code>: 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 <a href="https://testing-library.com/docs/react-testing-library/intro/"><code>@testing-library/react</code></a> or <a href="https://testing-library.com/docs/react-native-testing-library/intro"><code>@testing-library/react-native</code></a></li> </ul> <h3>Breaking Changes</h3> <p>React 19 brings in a number of breaking changes, including the removals of long-deprecated APIs. We recommend first upgrading to <code>18.3.1</code>, where we've added additional deprecation warnings. Check out the <a href="https://19.react.dev/blog/2024/04/25/react-19-upgrade-guide">upgrade guide</a> for more details and guidance on codemodding.</p> <h3>React</h3> <ul> <li>New JSX Transform is now required: We introduced <a href="https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html">a new JSX transform</a> 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.</li> <li>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 <code>onUncaughtError</code> and <code>onCaughtError</code> methods to <code>createRoot</code> and <code>hydrateRoot</code> to customize this error handling.</li> <li>Removed: <code>propTypes</code>: Using <code>propTypes</code> will now be silently ignored. If required, we recommend migrating to TypeScript or another type-checking solution.</li> <li>Removed: <code>defaultProps</code> for functions: ES6 default parameters can be used in place. Class components continue to support <code>defaultProps</code> since there is no ES6 alternative.</li> </ul>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/facebook/react/commit/e1378902bbb322aa1fe1953780f4b2b5f80d26b1"><code>e137890</code></a> [string-refs] cleanup string ref code (<a href="https://github.com/facebook/react/tree/HEAD/packages/react/issues/31443">#31443</a>)</li> <li><a href="https://github.com/facebook/react/commit/d1f04722d617600cc6cd96dcebc1c2ef7affc904"><code>d1f0472</code></a> [string-refs] remove enableLogStringRefsProd flag (<a href="https://github.com/facebook/react/tree/HEAD/packages/react/issues/31414">#31414</a>)</li> <li><a href="https://github.com/facebook/react/commit/3dc1e4820ec985baa6668a4fa799760c4b99f5d9"><code>3dc1e48</code></a> Followup: remove dead test code from <a href="https://github.com/facebook/react/tree/HEAD/packages/react/issues/30346">#30346</a> (<a href="https://github.com/facebook/react/tree/HEAD/packages/react/issues/31415">#31415</a>)</li> <li><a href="https://github.com/facebook/react/commit/07aa494432e97f63fca9faf2fad6f76fead31063"><code>07aa494</code></a> Remove enableRefAsProp feature flag (<a href="https://github.com/facebook/react/tree/HEAD/packages/react/issues/30346">#30346</a>)</li> <li><a href="https://github.com/facebook/react/commit/45804af18d589fd2c181f3b020f07661c46b73ea"><code>45804af</code></a> [flow] Eliminate usage of more than 1-arg <code>React.AbstractComponent</code> in React ...</li> <li><a href="https://github.com/facebook/react/commit/5636fad840942cfea80301d91e931a50c6370d19"><code>5636fad</code></a> [string-refs] log string ref from prod (<a href="https://github.com/facebook/react/tree/HEAD/packages/react/issues/31161">#31161</a>)</li> <li><a href="https://github.com/facebook/react/commit/b78a7f2f35e554a8647c3262d7f392e68d06febc"><code>b78a7f2</code></a> [rcr] Re-export useMemoCache in top level React namespace (<a href="https://github.com/facebook/react/tree/HEAD/packages/react/issues/31139">#31139</a>)</li> <li><a href="https://github.com/facebook/react/commit/4e9540e3c2a8f9ae56318b967939c99b3a815190"><code>4e9540e</code></a> [Fiber] Log the Render/Commit phases and the gaps in between (<a href="https://github.com/facebook/react/tree/HEAD/packages/react/issues/31016">#31016</a>)</li> <li><a href="https://github.com/facebook/react/commit/d4688dfaafe51a4cb6e3c51fc2330662cb4e2296"><code>d4688df</code></a> [Fiber] Track Event Time, startTransition Time and setState Time (<a href="https://github.com/facebook/react/tree/HEAD/packages/react/issues/31008">#31008</a>)</li> <li><a href="https://github.com/facebook/react/commit/15da9174518f18f82869767ebe2a21be2fc8bd90"><code>15da917</code></a> Don't read currentTransition back from internals (<a href="https://github.com/facebook/react/tree/HEAD/packages/react/issues/30991">#30991</a>)</li> <li>Additional commits viewable in <a href="https://github.com/facebook/react/commits/v19.0.0/packages/react">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=react&package-manager=npm_and_yarn&previous-version=18.3.1&new-version=19.0.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) You can trigger a rebase of this PR by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> > **Note** > Automatic rebases have been disabled on this pull request as it has been open for over 30 days. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>