build(deps): bump the npm-production-dependencies group across 4 directories with 57 updates

[dependabot]

Bumps the npm-production-dependencies group with 8 updates in the /src/flagd-ui directory:

Package	From	To
next	14.2.5	15.1.4
react	18.3.1	19.0.0
@types/react	18.3.4	19.0.3
react-dom	18.3.1	19.0.0
@types/react-dom	18.3.0	19.0.2
@opentelemetry/instrumentation	0.53.0	0.57.0
@opentelemetry/sdk-metrics	1.26.0	1.30.0
@opentelemetry/sdk-trace-base	1.26.0	1.30.0

Bumps the npm-production-dependencies group with 34 updates in the /src/frontend directory:

Package	From	To
next	14.2.5	15.1.4
react	18.3.1	19.0.0
@types/react	18.3.3	19.0.3
react-dom	18.3.1	19.0.0
@types/react-dom	18.3.0	19.0.2
@grpc/grpc-js	1.10.11	1.12.5
@openfeature/react-sdk	0.4.1	0.4.10
@opentelemetry/auto-instrumentations-node	0.48.0	0.55.1
@opentelemetry/auto-instrumentations-web	0.40.0	0.45.0
@opentelemetry/context-zone	1.25.1	1.30.0
@opentelemetry/core	1.25.1	1.30.0
@opentelemetry/exporter-metrics-otlp-grpc	0.52.1	0.57.0
@opentelemetry/exporter-trace-otlp-grpc	0.52.1	0.57.0
@opentelemetry/exporter-trace-otlp-http	0.52.1	0.57.0
@opentelemetry/instrumentation	0.52.1	0.57.0
@opentelemetry/resource-detector-alibaba-cloud	0.28.10	0.29.7
@opentelemetry/resource-detector-aws	1.5.2	1.10.0
@opentelemetry/resource-detector-container	0.3.11	0.5.3
@opentelemetry/resource-detector-gcp	0.29.10	0.32.0
@opentelemetry/resources	1.25.1	1.30.0
@opentelemetry/sdk-metrics	1.25.1	1.30.0
@opentelemetry/sdk-node	0.52.1	0.57.0
@opentelemetry/sdk-trace-base	1.25.1	1.30.0
@opentelemetry/sdk-trace-node	1.25.1	1.30.0
@opentelemetry/sdk-trace-web	1.25.1	1.30.0
@tanstack/react-query	4.36.1	5.62.16
cookies-next	4.2.1	5.0.2
dotenv	16.4.5	16.4.7
dotenv-expand	11.0.6	12.0.1
sharp	0.33.4	0.33.5
styled-components	6.1.11	6.1.14
ts-proto	1.181.1	2.6.1
uuid	10.0.0	11.0.4
@openfeature/server-sdk	1.15.0	1.17.0

Bumps the npm-production-dependencies group with 16 updates in the /src/payment directory:

Package	From	To
@grpc/grpc-js	1.10.11	1.12.5
@opentelemetry/auto-instrumentations-node	0.54.0	0.55.1
@opentelemetry/core	1.29.0	1.30.0
@opentelemetry/exporter-metrics-otlp-grpc	0.56.0	0.57.0
@opentelemetry/exporter-trace-otlp-grpc	0.56.0	0.57.0
@opentelemetry/resource-detector-alibaba-cloud	0.29.6	0.29.7
@opentelemetry/resource-detector-aws	1.9.0	1.10.0
@opentelemetry/resource-detector-container	0.5.2	0.5.3
@opentelemetry/resource-detector-gcp	0.31.0	0.32.0
@opentelemetry/resources	1.29.0	1.30.0
@opentelemetry/sdk-metrics	1.29.0	1.30.0
@opentelemetry/sdk-node	0.56.0	0.57.0
uuid	11.0.3	11.0.4
@openfeature/server-sdk	1.16.2	1.17.0
@opentelemetry/instrumentation-runtime-node	0.11.0	0.12.0
pino	9.5.0	9.6.0

Bumps the npm-production-dependencies group with 33 updates in the /src/react-native-app directory:

Package	From	To
react	18.2.0	19.0.0
@types/react	18.2.79	19.0.3
react-dom	18.2.0	19.0.0
@opentelemetry/core	1.28.0	1.30.0
@opentelemetry/exporter-trace-otlp-http	0.52.1	0.57.0
@opentelemetry/instrumentation	0.55.0	0.57.0
@opentelemetry/resources	1.28.0	1.30.0
@opentelemetry/sdk-trace-base	1.28.0	1.30.0
@opentelemetry/sdk-trace-web	1.28.0	1.30.0
@tanstack/react-query	4.36.1	5.62.16
dotenv	16.4.5	16.4.7
ts-proto	1.181.1	2.6.1
uuid	10.0.0	11.0.4
@expo/metro-config	0.19.4	0.19.8
@opentelemetry/instrumentation-fetch	0.55.0	0.57.0
@opentelemetry/instrumentation-xml-http-request	0.55.0	0.57.0
@react-navigation/native	6.1.18	7.0.14
expo	51.0.39	52.0.23
expo-constants	16.0.2	17.0.3
expo-font	12.0.10	13.0.2
expo-linking	6.3.1	7.0.3
expo-router	3.5.24	4.0.15
expo-splash-screen	0.27.7	0.29.18
expo-status-bar	1.12.1	2.0.0
expo-system-ui	3.0.7	4.0.6
expo-web-browser	13.0.3	14.0.1
react-hook-form	7.53.2	7.54.2
react-native	0.74.2	0.76.5
react-native-device-info	11.1.0	14.0.2
react-native-gesture-handler	2.16.2	2.21.2
react-native-reanimated	3.10.1	3.16.6
react-native-safe-area-context	4.10.1	5.0.0
react-native-screens	3.31.1	4.4.0

Updates next from 14.2.5 to 15.1.4

Release notes

Sourced from next's releases.

v15.1.4

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• backport: force module format for virtual client-proxy (#74608)
• Fix prerender tags when notFound is called (#74607)
• Use provided waitUntil for pending revalidates (#74604)
• Feature: next/image: add support for images.qualities in next.config (#74588)
• Chore: docs: add missing search: '' on remotePatterns (#74587)
• Chore: docs: update version history of next/image (#73923) (#74570)
• Chore: next/image: improve imgopt api bypass detection for unsupported images (#74569)

Credits

Huge thanks to @ and @ for helping!

v15.1.3

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• Retry manifest file loading only in dev mode: #73900
• Use shared worker for lint & typecheck steps: #74154

Credits

Huge thanks to @​unstubbable and @​ztanner for helping!

v15.1.2

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• Update React from 7283a213-20241206 to 65e06cb7-20241218: vercel/next.js#74117

Credits

Huge thanks to @​ztanner for helping!

v15.1.1

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• fix(turbo): sassOptions silenceDeprecations was not overwritten with user options: vercel/next.js#73937
• refactor collectAppPageSegments: vercel/next.js#73908

Credits

... (truncated)

Commits

• 48f2588 v15.1.4
• dcb208e backport: force module format for virtual client-proxy (#74162) (#74608)
• 6f6766a Fix prerender tags when notFound is called (#74577) (#74607)
• a46f27f Use provided waitUntil for pending revalidates (#74164) (#74604)
• bc6acf6 feat(next/image): add support for images.qualities in next.config (#74588)
• d253ac5 chore(docs): add missing search: '' on remotePatterns (#73925) (#74587)
• 7b195a8 chore(docs): update version history of next/image (#73923) (#74570)
• 5a501d3 chore(next/image): improve imgopt api bypass detection for unsupported images...
• 4cbaaa1 v15.1.3
• 221d18b Backport v15: used shared worker for lint & typecheck steps (#74154) (#74285)
• 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 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

Updates @types/react from 18.3.4 to 19.0.3

Commits

• See full diff in compare view

Updates react-dom from 18.3.1 to 19.0.0

Release notes

Sourced from react-dom'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-dom'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 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

• 989af12 Make prerendering always non-blocking with fix (#31452)
• e137890 [string-refs] cleanup string ref code (#31443)
• 07aa494 Remove enableRefAsProp feature flag (#30346)
• cae764c Revert "[Re-land] Make prerendering always non-blocking (#31268)" (#31355)
• d49123f Expose prerender() for SSG in stable (#31298)
• 6c4bbc7 [Re-land] Make prerendering always non-blocking (#31268)
• d8c90fa Disable infinite render loop detection (#31088)
• 67fee58 [Fizz] Start initial work immediately (#31079)
• 76aee6f Revert "Make prerendering always non-blocking" (#31080)
• 0f1856c Make prerendering always non-blocking (#31056)
• Additional commits viewable in compare view

Updates @types/react-dom from 18.3.0 to 19.0.2

Commits

• See full diff in compare view

Updates @opentelemetry/instrumentation from 0.53.0 to 0.57.0

Release notes

Sourced from @​opentelemetry/instrumentation's releases.

experimental/v0.57.0

0.57.0

🚀 (Enhancement)

• feat(opentelemetry-sdk-node): automatically configure metrics exporter based on environment variables #5168 @​bhaskarbanerjee

🏠 (Internal)

• refactor(otlp-transformer): re-structure package to prepare for separate entrypoints #5264 @​pichlermarc

experimental/v0.56.0

0.56.0

💥 Breaking Change

• feat(otlp-exporter-base)!: collapse base classes into one #5031 @​pichlermarc
  • OTLPExporterNodeBase has been removed in favor of a platform-agnostic implementation (OTLPExporterBase)
  • OTLPExporterBrowserBase has been removed in favor of a platform-agnostic implementation (OTLPExporterBase)
  • ExportServiceError was intended for internal use and has been dropped from exports
  • validateAndNormalizeHeaders was intended for internal use and has been dropped from exports
  • OTLPExporterBase all properties are now private, the constructor now takes an IOTLPExportDelegate, the type parameter for config type has been dropped.
    • This type is scheduled for removal in a future version of this package, please treat all exporters as SpanExporter, PushMetricExporter or LogRecordExporter, based on their respective type.
• feat(otlp-grpc-exporter-base)!: collapse base classes into one #5031 @​pichlermarc
  • OTLPGRPCExporterNodeBase has been removed in favor of a platform-agnostic implementation (OTLPExporterBase from @opentelemetry/otlp-exporter-base)
• feat(otlp-transformer)!: accept ResourceMetrics in serializers instead of ResourceMetrics[]
  • (user-facing): ProtobufMetricsSerializer now only accepts ResourceMetrics instead of ResourceMetrics[] to align with PushMetricExporter requirements
  • (user-facing): JsonMetricsSerializer now only accepts ResourceMetrics instead of ResourceMetrics[] to align with PushMetricExporter requirements

🚀 (Enhancement)

• feat(otlp-exporter-base): handle OTLP partial success #5183 @​pichlermarc
• feat(otlp-exporter-base): internally accept a http header provider function only #5179 @​pichlermarc
• refactor(otlp-exporter-base): don't create blob before sending xhr #5193 @​pichlermarc
  • improves compatibility with some unsupported runtimes
• feat(otlp-exporter-base): add http response body to exporter error #5204 @​pichlermarc

🐛 (Bug Fix)

• fix(otlp-exporter-*): de-confuse Nuxt build tooling by not using 'export *' in comments #5227 @​pichlermarc

🏠 (Internal)

• chore(otlp-exporter-*-grpc): clean up tests #5196 @​pichlermarc
• chore(otlp-exporter-*-http): clean up tests #5196 @​pichlermarc
• chore(otlp-exporter-*-proto): clean up tests #5196 @​pichlermarc

experimental/v0.55.0

... (truncated)

Commits

• 616d27a chore: prepare next release (#5274)
• e524148 chore: removed circular dependency from BasicTracerProvider (#5279)
• 67a0e9c Update links to openmetrics to reference the v1.0.0 release (#5267)
• 0c11fc6 Fix incorrect CHANGELOG entry on main (v1.next) (#5280)
• 8ab52d5 fix(ci): adapt workflow to use supported npm versions (#5277)
• 84cce75 refactor(otlp-transformer): re-structure package to prepare for separate entr...
• 6d31a18 feat(opentelemetry-sdk-node): automatically configure metrics exporter based ...
• e03b6e7 chore: update prettier to 3.4.2 (#5261)
• e4d9c21 fix(instrumentation-fetch, instrumentation-xml-http-request) content length a...
• bdee949 doc(semantic-conventions): clarify suggested usage of unstable semconv (#5256)
• Additional commits viewable in compare view

Updates @opentelemetry/sdk-metrics from 1.26.0 to 1.30.0

Release notes

Sourced from @​opentelemetry/sdk-metrics's releases.

v1.30.0

1.30.0

🚀 (Enhancement)

• feat(sdk-metrics): PeriodicExportingMetricReader now flushes pending tasks at shutdown #5242

🐛 (Bug Fix)

• fix(sdk-trace-base): do not load OTEL_ env vars on module load, but when needed #5233
• fix(instrumentation-xhr, instrumentation-fetch): content length attributes no longer get removed with ignoreNetworkEvents: true being set #5229

v1.29.0

1.29.0

🚀 (Enhancement)

• feat(sdk-metrics): Add support for aggregation cardinality limit with a default limit of 2000. This limit can be customized via views #5128

v1.28.0

1.28.0

🚀 (Enhancement)

...

Description has been truncated