Skip to content

Update react monorepo (major) - #143

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-react-monorepo
Open

Update react monorepo (major)#143
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-react-monorepo

Conversation

@renovate

@renovate renovate Bot commented Oct 12, 2024 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@types/react (source) ^18.2.0 → ^19.0.0 age confidence
@types/react-dom (source) ^18.2.0 → ^19.0.0 age confidence
eslint-plugin-react-hooks (source) ^4.6.2 → ^7.0.0 age confidence
react (source) ^16.13.1 → ^16.13.1 || ^19.0.0 age confidence
react (source) ^18.2.0 → ^19.0.0 age confidence
react-dom (source) ^18.2.0 → ^19.0.0 age confidence

Release Notes

facebook/react (eslint-plugin-react-hooks)

v7.1.1

Compare Source

Note: 7.1.0 accidentally removed the component-hook-factories rule, causing errors for users who referenced it in their ESLint config. This is now fixed.

  • Add deprecated no-op component-hook-factories rule for backwards compatibility. (@​mofeiZ in #​36307)

v7.1.0

Compare Source

This release adds ESLint v10 support, improves performance by skipping compilation for non-React files, and includes compiler lint improvements including better set-state-in-effect detection, improved ref validation, and more helpful error reporting.

v7.0.1

Compare Source

v7.0.0

Compare Source

This release slims down presets to just 2 configurations (recommended and recommended-latest), and all compiler rules are enabled by default.

  • Breaking: Removed recommended-latest-legacy and flat/recommended configs. The plugin now provides recommended (legacy and flat configs with all recommended rules), and recommended-latest (legacy and flat configs with all recommended rules plus new bleeding edge experimental compiler rules). (@​poteto in #​34757)

v6.1.1

Compare Source

Note: 6.1.0 accidentally allowed use of recommended without flat config, causing errors when used with ESLint v9's defineConfig() helper. This has been fixed in 6.1.1.

v6.1.0

Compare Source

Note: Version 6.0.0 was mistakenly released and immediately deprecated and untagged on npm. This is the first official 6.x major release and includes breaking changes.

  • Breaking: Require Node.js 18 or newer. (@​michaelfaith in #​32458)
  • Breaking: Flat config is now the default recommended preset. Legacy config moved to recommended-legacy. (@​michaelfaith in #​32457)
  • New Violations: Disallow calling use within try/catch blocks. (@​poteto in #​34040)
  • New Violations: Disallow calling useEffectEvent functions in arbitrary closures. (@​jbrown215 in #​33544)
  • Handle React.useEffect in addition to useEffect in rules-of-hooks. (@​Ayc0 in #​34076)
  • Added react-hooks settings config option that to accept additionalEffectHooks that are used across exhaustive-deps and rules-of-hooks rules. (@​jbrown215) in #​34497

v6.0.0

Compare Source

Accidentally released. See 6.1.0 for the actual changes.

v5.2.0

Compare Source

v5.1.0

Compare Source

v5.0.0

Compare Source

  • New Violations: Component names now need to start with an uppercase letter instead of a non-lowercase letter. This means _Button or _component are no longer valid. (@​kassens) in #​25162
react/react (react)

v19.2.8

Compare Source

v19.2.7

Compare Source

React Server Components

v19.2.6

Compare Source

React Server Components

v19.2.5

Compare Source

React Server Components

v19.2.4

Compare Source

React Server Components

v19.2.3

Compare Source

React Server Components

v19.2.2

Compare Source

React Server Components

v19.2.1

Compare Source

React Server Components

v19.2.0

Compare Source

Below is a list of all new features, APIs, and bug fixes.

Read the React 19.2 release post for more information.

New React Features
  • <Activity>: A new API to hide and restore the UI and internal state of its children.
  • useEffectEvent is a React Hook that lets you extract non-reactive logic into an Effect Event.
  • cacheSignal (for RSCs) lets your know when the cache() lifetime is over.
  • React Performance tracks appear on the Performance panel’s timeline in your browser developer tools
New React DOM Features
  • Added resume APIs for partial pre-rendering with Web Streams:
  • Added resume APIs for partial pre-rendering with Node Streams:
  • Updated prerender APIs to return a postponed state that can be passed to the resume APIs.
Notable changes
  • React DOM now batches suspense boundary reveals, matching the behavior of client side rendering. This change is especially noticeable when animating the reveal of Suspense boundaries e.g. with the upcoming <ViewTransition> Component. React will batch as much reveals as possible before the first paint while trying to hit popular first-contentful paint metrics.
  • Add Node Web Streams (prerender, renderToReadableStream) to server-side-rendering APIs for Node.js
  • Use underscore instead of : IDs generated by useId
All Changes
React
React DOM
React Server Components
React Reconciler

v19.1.9

Compare Source

v19.1.8

Compare Source

React Server Components

v19.1.7

Compare Source

React Server Components

v19.1.6

Compare Source

React Server Components

v19.1.5

Compare Source

React Server Components

v19.1.4

Compare Source

React Server Components

v19.1.3

Compare Source

React Server Components

v19.1.2

Compare Source

React Server Components

v19.1.1

Compare Source

React

v19.1.0

Compare Source

Owner Stack

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

  • An Owner Stack is a development-only stack trace that helps identify which components are responsible for rendering a particular component. An Owner Stack is distinct from a Component Stacks, which shows the hierarchy of components leading to an error.
  • The captureOwnerStack API is only available in development mode and returns a Owner Stack, if available. The API can be used to enhance error overlays or log component relationships when debugging. #​29923, #​32353, #​30306,
    #​32538, #​32529, #​32538
React
  • Enhanced support for Suspense boundaries to be used anywhere, including the client, server, and during hydration. #​32069, #​32163, #​32224, #​32252
  • Reduced unnecessary client rendering through improved hydration scheduling #​31751
  • Increased priority of client rendered Suspense boundaries #​31776
  • Fixed frozen fallback states by rendering unfinished Suspense boundaries on the client. #​31620
  • Reduced garbage collection pressure by improving Suspense boundary retries. #​31667
  • Fixed erroneous “Waiting for Paint” log when the passive effect phase was not delayed #​31526
  • Fixed a regression causing key warnings for flattened positional children in development mode. #​32117
  • Updated useId to use valid CSS selectors, changing format from :r123: to «r123». #​32001
  • Added a dev-only warning for null/undefined created in useEffect, useInsertionEffect, and useLayoutEffect. #​32355
  • Fixed a bug where dev-only methods were exported in production builds. React.act is no longer available in production builds. #​32200
  • Improved consistency across prod and dev to improve compatibility with Google Closure Compiler and bindings #​31808
  • Improve passive effect scheduling for consistent task yielding. #​31785
  • Fixed asserts in React Native when passChildrenWhenCloningPersistedNodes is enabled for OffscreenComponent rendering. #​32528
  • Fixed component name resolution for Portal #​32640
  • Added support for beforetoggle and toggle events on the dialog element. #​32479
React DOM
  • Fixed double warning when the href attribute is an empty string #​31783
  • Fixed an edge case where getHoistableRoot() didn’t work properly when the container was a Document #​32321
  • Removed support for using HTML comments (e.g. <!-- -->) as a DOM container. #​32250
  • Added support for <script> and <template> tags to be nested within <select> tags. #​31837
  • Fixed responsive images to be preloaded as HTML instead of headers #​32445
use-sync-external-store
  • Added exports field to package.json for use-sync-external-store to support various entrypoints. #​25231
React Server Components
  • Added unstable_prerender, a new experimental API for prerendering React Server Components on the server #​31724
  • Fixed an issue where streams would hang when receiving new chunks after a global error #​31840, #​31851
  • Fixed an issue where pending chunks were counted twice. #​31833
  • Added support for streaming in edge environments #​31852
  • Added support for sending custom error names from a server so that they are available in the client for console replaying. #​32116
  • Updated the server component wire format to remove IDs for hints and console.log because they have no return value #​31671
  • Exposed registerServerReference in client builds to handle server references in different environments. #​32534
  • Added react-server-dom-parcel package which integrates Server Components with the Parcel bundler #​31725, #​32132, #​31799, #​32294, #​31741

v19.0.8

Compare Source

v19.0.7

Compare Source

React Server Components

v19.0.6

Compare Source

React Server Components

v19.0.5

Compare Source

React Server Components

v19.0.4

Compare Source

React Server Components

v19.0.3

Compare Source

React Server Components

v19.0.2

Compare Source

React Server Components

v19.0.1

Compare Source

React Server Components

v19.0.0

Compare Source

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.
  • Removed: contextTypes and getChildContext: Legacy Context for class components has been removed in favor of the contextType API.
  • Removed: string refs: Any usage of string refs need to be migrated to ref callbacks.
  • Removed: Module pattern factories: A rarely used pattern that can be migrated to regular functions.
  • Removed: React.createFactory: Now that JSX is broadly supported, all createFactory usage can be migrated to JSX components.
  • Removed: react-test-renderer/shallow: This has been a re-export of react-shallow-renderer since React 18. If needed, you can continue to use the third-party package directly. We recommend using @​testing-library/react or @​testing-library/react-native instead.
React DOM
  • Removed: react-dom/test-utils: We’ve moved act from react-dom/test-utils to react. All other utilities have been removed.
  • Removed: ReactDOM.render, ReactDOM.hydrate: These have been removed in favor of the concurrent equivalents: ReactDOM.createRoot and ReactDOM.hydrateRoot.
  • Removed: unmountComponentAtNode: Removed in favor of root.unmount().
  • Removed: ReactDOM.findDOMNode: You can replace ReactDOM.findDOMNode with DOM Refs.
Notable Changes
React
  • <Context> as a provider: You can now render <Context> as a provider instead of <Context.Provider>.
  • Cleanup functions for refs: When the component unmounts, React will call the cleanup function returned from the ref callback.
  • useDeferredValue initial value argument: When provided, useDeferredValue will return the initial value for the initial render of a component, then schedule a re-render in the background with the deferredValue returned.
  • Support for Custom Elements: React 19 now passes all tests on Custom Elements Everywhere.
  • StrictMode changes: useMemo and useCallback will now reuse the memoized results from the first render, during the second render. Additionally, StrictMode will now double-invoke ref callback functions on initial mount.
  • UMD builds removed: To load React 19 with a script tag, we recommend using an ESM-based CDN such as esm.sh.
React DOM
  • Diffs for hydration errors: In the case of a mismatch, React 19 logs a single error with a diff of the mismatched content.
  • Compatibility with third-party scripts and extensions: React will now force a client re-render to fix up any mismatched content caused by elements inserted by third-party JS.
TypeScript Changes

The most common changes can be codemodded with npx types-react-codemod@latest preset-19 ./path-to-your-react-ts-files.

  • Removed deprecated TypeScript types:
    • ReactChild (replacement: React.ReactElement | number | string)
    • ReactFragment (replacement: Iterable<React.ReactNode>)
    • ReactNodeArray (replacement: ReadonlyArray<React.ReactNode>)
    • ReactText (replacement: number | string)
    • VoidFunctionComponent (replacement: FunctionComponent)
    • VFC (replacement: FC)
    • Moved to prop-types: Requireable, ValidationMap, Validator, WeakValidationMap
    • Moved to create-react-class: ClassicComponentClass, ClassicComponent, ClassicElement, ComponentSpec, Mixin, ReactChildren, ReactHTML, ReactSVG, SFCFactory
  • Disallow implicit return in refs: refs can now accept cleanup functions. When you return something else, we can’t tell if you intentionally returned something not meant to clean up or returned the wrong value. Implicit returns of anything but functions will now error.
  • Require initial argument to useRef: The initial argument is now required to match useState, createContext etc
  • Refs are mutable by default: Ref objects returned from useRef() are now always mutable instead of sometimes being immutable. This feature was too confusing for users and conflicted with legit cases where refs were managed by React and manually written to.
  • Strict ReactElement typing: The props of React elements now default to unknown instead of any if the element is typed as ReactElement
  • JSX namespace in TypeScript: The global JSX namespace is removed to improve interoperability with other libraries using JSX. Instead, the JSX namespace is available from the React package: import { JSX } from 'react'
  • Better useReducer typings: Most useReducer usage should not require explicit type arguments.
    For example, 
    -useReducer<React.Reducer<State, Action>>(reducer)
+useReducer(reducer)
    or 
    -useReducer<React.Reducer<State, Action>>(reducer)
+useReducer<State, Action>(reducer)
All Changes
React
  • Add support for as

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (in timezone US/Eastern)

  • Branch creation
    • "every weekend"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 5 times, most recently from 4f56489 to 66b9017 Compare October 18, 2024 13:46
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 5 times, most recently from d6bc9ff to 18d5449 Compare October 23, 2024 15:37
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from 18d5449 to 954e234 Compare November 4, 2024 09:44
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from 954e234 to 438a1d2 Compare November 11, 2024 10:34
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from f4dd64f to 61c0f6a Compare November 22, 2024 15:33
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from 61c0f6a to 0f0d190 Compare November 25, 2024 12:04
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from c905fe6 to 941259e Compare December 9, 2024 11:41
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from 941259e to 5ff7d9f Compare December 16, 2024 09:14
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 0d0583c to 7eb8c50 Compare December 30, 2024 06:14
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from 7eb8c50 to a308446 Compare January 6, 2025 07:13
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from a308446 to 1db2c9b Compare January 13, 2025 11:07
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from 1db2c9b to 396de6c Compare January 20, 2025 11:26
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 57ee518 to bc6ea8f Compare February 3, 2025 10:26
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from bc6ea8f to c6d6a72 Compare February 10, 2025 10:59
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from dcbe2ce to a63e85d Compare February 24, 2025 09:01
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 4 times, most recently from abf67fe to 9a09352 Compare October 3, 2025 22:14
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 4 times, most recently from d390067 to 28c1cd6 Compare October 13, 2025 15:51
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 4 times, most recently from a56867a to 7e3874d Compare October 24, 2025 21:13
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from 157f096 to 50cfab3 Compare October 29, 2025 17:14
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 5 times, most recently from 6717843 to dc4d274 Compare November 18, 2025 04:52
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from dc4d274 to b04e905 Compare November 24, 2025 11:16
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from b04e905 to 242214a Compare December 3, 2025 16:47
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from c64fae2 to e31f1ea Compare December 12, 2025 04:59
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from e31f1ea to f0471e3 Compare December 31, 2025 18:51
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 0d85717 to 3a97756 Compare January 10, 2026 10:08
sentry[bot]
sentry Bot reviewed Mar 2, 2026
View reviewed changes
Comment thread package.json Outdated
Comment on lines 89 to 91
"react": "^19.0.0",
"react-router": "^6.22.2"
},

@sentry sentry Bot Mar 2, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: The package specifies incompatible peer dependencies for react (^19.0.0) and next (^14.2.7), which will break usage for consumers of the Next.js integration.
Severity: HIGH

Suggested Fix

To resolve the conflict, either downgrade the react and react-dom peer dependencies to a version compatible with Next.js 14 (e.g., ^18.2.0), or update the next peer dependency to a version that supports React 19 (e.g., ^15.1.0).

Prompt for AI Agent 
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: package.json#L89-L91

Potential issue: The library's `package.json` specifies `react: ^19.0.0` as a peer
dependency while also listing `next: ^14.2.7` as an optional peer dependency. Official
documentation confirms that Next.js 14 is not compatible with React 19; support was
added in Next.js 15.1. This creates an impossible dependency resolution scenario for
consumers who use the library's Next.js-specific features, such as the `useSearchParams`
hook. Attempting to use the Next.js integration with Next.js 14 will result in peer
dependency conflicts and likely runtime errors due to the underlying incompatibility.

Did we get this right? 👍 / 👎 to inform future reviews.

sentry[bot]
sentry Bot reviewed Mar 6, 2026
View reviewed changes
Comment thread package.json Outdated
"@types/history": "^4.9",
"next": "^14.2.7",
"react": "^16.13.1",
"react": "^19.0.0",

@sentry sentry Bot Mar 6, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: The react peer dependency is too restrictive, requiring version ^19.0.0. This will break installation for consumers using React 16, 17, or 18.
Severity: HIGH

Suggested Fix

To maintain backward compatibility, the react peer dependency should be broadened to include older, still-compatible versions. A suitable range would be ^16.13.1 || ^17.0.0 || ^18.0.0 || ^19.0.0, allowing projects using React 16 through 19 to install and use the library.

Prompt for AI Agent 
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: package.json#L89

Potential issue: The `react` peer dependency has been updated from `^16.13.1` to
`^19.0.0`. However, the library's source code does not use any React 19-specific
features and remains compatible with older versions like React 16, 17, and 18. This
change is overly restrictive and constitutes a breaking change for downstream consumers
who are not on React 19. Their package manager will fail to install this library due to
the unmet peer dependency, preventing them from receiving updates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@sentry sentry[bot] sentry[bot] left review comments

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants