Skip to content

fix(deps): update react monorepo (major)#3484

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

fix(deps): update react monorepo (major)#3484
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/major-react-monorepo

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 18, 2025 •
edited
Loading

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@types/react (source) ^18.3.3 → ^19.0.0 age confidence
@types/react-dom (source) ^18.3.0 → ^19.0.0 age confidence
eslint-plugin-react-hooks (source) ^5.2.0 → ^7.0.0 age confidence
react (source) ^18.3.1 → ^19.0.0 age confidence
react-dom (source) ^18.3.1 → ^19.0.0 age confidence
react-test-renderer (source) ^18.2.0 → ^19.0.0 age confidence

Release Notes

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

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.

facebook/react (react)

v19.2.4: 19.2.4 (January 26th, 2026)

Compare Source

React Server Components

v19.2.3: 19.2.3 (December 11th, 2025)

Compare Source

React Server Components

v19.2.2: 19.2.2 (December 11th, 2025)

Compare Source

React Server Components

v19.2.1: 19.2.1 (December 3rd, 2025)

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.5: 19.1.5 (January 26th, 2026)

Compare Source

React Server Components

v19.1.4: 19.1.4 (December 11th, 2025)

Compare Source

React Server Components

v19.1.3: 19.1.3 (December 11th, 2025)

Compare Source

React Server Components

v19.1.2: 19.1.2 (December 3rd, 2025)

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.4: 19.0.4 (January 26th, 2026)

Compare Source

React Server Components

v19.0.3: 19.0.3 (December 11th, 2025)

Compare Source

React Server Components

v19.0.2: 19.0.2 (December 11th, 2025)

Compare Source

React Server Components

v19.0.1: 19.0.1 (December 3rd, 2025)

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

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR becomes conflicted, 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 added the dependencies This pull request updates dependency files label Dec 18, 2025
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from bb0e592 to 55d9ee4 Compare December 18, 2025 21:00
sentry[bot]
sentry bot reviewed Dec 18, 2025
View reviewed changes
yarn.lock Outdated
Comment on lines 11704 to 11714
version: 19.2.3
resolution: "react-test-renderer@npm:19.2.3"
dependencies:
react-is: "npm:^18.3.1"
react-shallow-renderer: "npm:^16.15.0"
scheduler: "npm:^0.23.2"
react-is: "npm:^19.2.3"
scheduler: "npm:^0.27.0"
peerDependencies:
react: ^18.3.1
checksum: 10c0/c633558ef9af33bc68f0c4dbb5163a004c4fb9eade7bd0a7cfc0355fb367f36bd9d96533c90b7e85a146be6c525113a15f58683d269e0177ad77e2b04d4fe51c
react: ^19.2.3
checksum: 10c0/842b82239dbddbc536083a6260c3e1b0507c02a3400bd05879fc19160468fd0f8ab79fec5dceffa6113b131835cc7621212f8415b46ea5156ab66bbfd7e24297
languageName: node
linkType: hard

This comment was marked as outdated.

Sign in to view

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from e2769db to bae9636 Compare December 18, 2025 21:13
sentry[bot]
sentry bot reviewed Dec 18, 2025
View reviewed changes
package.json
"@types/react-dom": "^19.0.0",
"@types/react-redux": "^7.1.24",
"@types/react-syntax-highlighter": "^15.5.7",
"@types/react-test-renderer": "^18.0.0",

This comment was marked as outdated.

Sign in to view

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from bae9636 to ac529ee Compare December 18, 2025 21:24
sentry[bot]
sentry bot reviewed Dec 18, 2025
View reviewed changes
package.json
Comment on lines 140 to 148
"@types/js-cookie": "^3.0.6",
"@types/js-yaml": "^4.0.5",
"@types/lodash": "^4.14.195",
"@types/react": "^18.3.3",
"@types/react": "^19.0.0",
"@types/react-copy-to-clipboard": "^5.0.4",
"@types/react-dom": "^18.3.0",
"@types/react-dom": "^19.0.0",
"@types/react-redux": "^7.1.24",
"@types/react-syntax-highlighter": "^15.5.7",
"@types/react-test-renderer": "^18.0.0",

This comment was marked as outdated.

Sign in to view

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from ac529ee to 53c67d2 Compare December 18, 2025 21:42
sentry[bot]
sentry bot reviewed Dec 18, 2025
View reviewed changes
package.json
"@types/react-dom": "^19.0.0",
"@types/react-redux": "^7.1.24",
"@types/react-syntax-highlighter": "^15.5.7",
"@types/react-test-renderer": "^18.0.0",

This comment was marked as outdated.

Sign in to view

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 53c67d2 to 0626d16 Compare December 18, 2025 21:48
sentry[bot]
sentry bot reviewed Dec 18, 2025
View reviewed changes
package.json
"process": "^0.11.10",
"react-error-overlay": "^6.0.11",
"react-test-renderer": "^18.2.0",
"react-test-renderer": "^19.0.0",

This comment was marked as outdated.

Sign in to view

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 0626d16 to 8333110 Compare December 21, 2025 18:48
sentry[bot]
sentry bot reviewed Dec 21, 2025
View reviewed changes
package.json
"@types/react-dom": "^19.0.0",
"@types/react-redux": "^7.1.24",
"@types/react-syntax-highlighter": "^15.5.7",
"@types/react-test-renderer": "^18.0.0",

This comment was marked as outdated.

Sign in to view

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from 03978a1 to cc2f1c4 Compare December 26, 2025 05:41
sentry[bot]
sentry bot reviewed Dec 26, 2025
View reviewed changes
package.json
Comment on lines 140 to 148
"@types/js-cookie": "^3.0.6",
"@types/js-yaml": "^4.0.5",
"@types/lodash": "^4.14.195",
"@types/react": "^18.3.3",
"@types/react": "^19.0.0",
"@types/react-copy-to-clipboard": "^5.0.4",
"@types/react-dom": "^18.3.0",
"@types/react-dom": "^19.0.0",
"@types/react-redux": "^7.1.24",
"@types/react-syntax-highlighter": "^15.5.7",
"@types/react-test-renderer": "^18.0.0",

This comment was marked as outdated.

Sign in to view

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 5 times, most recently from d3a3a1e to 7091ed7 Compare December 31, 2025 16:00
sentry[bot]
sentry bot reviewed Dec 31, 2025
View reviewed changes
package.json
"@types/react-dom": "^19.0.0",
"@types/react-redux": "^7.1.24",
"@types/react-syntax-highlighter": "^15.5.7",
"@types/react-test-renderer": "^18.0.0",

This comment was marked as outdated.

Sign in to view

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 7091ed7 to 96ed32a Compare January 8, 2026 20:10
sentry[bot]
sentry bot reviewed Jan 8, 2026
View reviewed changes
package.json Outdated
Comment on lines 77 to 87
"phaser": "~3.90.0",
"query-string": "^9.0.0",
"re-resizable": "^6.9.9",
"react": "^18.3.1",
"react": "^19.0.0",
"react-ace": "^14.0.0",
"react-copy-to-clipboard": "^5.1.0",
"react-debounce-render": "^8.0.2",
"react-dom": "^18.3.1",
"react-dom": "^19.0.0",
"react-drag-drop-files": "^3.0.0",
"react-draggable": "^4.4.5",
"react-dropzone": "^14.2.3",

This comment was marked as outdated.

Sign in to view

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from 849b02c to 2d3b44f Compare January 12, 2026 13:27
sentry[bot]
sentry bot reviewed Jan 12, 2026
View reviewed changes
package.json
Comment on lines +80 to +84
"react": "^19.0.0",
"react-ace": "^14.0.0",
"react-copy-to-clipboard": "^5.1.0",
"react-debounce-render": "^8.0.2",
"react-dom": "^18.3.1",
"react-dom": "^19.0.0",

This comment was marked as outdated.

Sign in to view

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 13 times, most recently from 04c549e to bb9ae6c Compare February 2, 2026 09:47
sentry[bot]
sentry bot reviewed Feb 2, 2026
View reviewed changes
package.json
"@types/react-dom": "^19.0.0",
"@types/react-redux": "^7.1.24",
"@types/react-syntax-highlighter": "^15.5.7",
"@types/react-test-renderer": "^18.0.0",

This comment was marked as outdated.

Sign in to view

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from c0f8f64 to 472e451 Compare February 4, 2026 09:10
sentry[bot]
sentry bot reviewed Feb 4, 2026
View reviewed changes
package.json Outdated
Comment on lines 77 to 87
"phaser": "~3.90.0",
"query-string": "^9.0.0",
"re-resizable": "^6.9.9",
"react": "^18.3.1",
"react": "^19.0.0",
"react-ace": "^14.0.0",
"react-copy-to-clipboard": "^5.1.0",
"react-debounce-render": "^8.0.2",
"react-dom": "^18.3.1",
"react-dom": "^19.0.0",
"react-drag-drop-files": "^3.0.0",
"react-draggable": "^4.4.5",
"react-dropzone": "^14.2.3",

This comment was marked as outdated.

Sign in to view

sentry[bot]
sentry bot reviewed Feb 20, 2026
View reviewed changes
package.json
"@types/react-dom": "^19.0.0",
"@types/react-redux": "^7.1.24",
"@types/react-syntax-highlighter": "^15.5.7",
"@types/react-test-renderer": "^18.0.0",

This comment was marked as outdated.

Sign in to view

sentry[bot]
sentry bot reviewed Feb 26, 2026
View reviewed changes
package.json
Comment on lines 139 to 147
"@types/js-cookie": "^3.0.6",
"@types/js-yaml": "^4.0.5",
"@types/lodash": "^4.14.195",
"@types/react": "^18.3.3",
"@types/react": "^19.0.0",
"@types/react-copy-to-clipboard": "^5.0.4",
"@types/react-dom": "^18.3.0",
"@types/react-dom": "^19.0.0",
"@types/react-redux": "^7.1.24",
"@types/react-syntax-highlighter": "^15.5.7",
"@types/react-test-renderer": "^18.0.0",
Copy link

@sentry sentry bot Feb 26, 2026

Choose a reason for hiding this comment

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

Bug: The react-sortable-hoc library is incompatible with React 19 as it uses the removed findDOMNode API, which will cause a runtime crash in the Chapter Publisher feature.
Severity: HIGH

Suggested Fix

The react-sortable-hoc library is unmaintained and incompatible with React 19. It should be replaced with a modern, maintained alternative, such as @dnd-kit, which is the recommended migration path by the original library's authors.

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#L139-L147

Potential issue: The upgrade to React 19 introduces a breaking change that will cause a
runtime crash in the Chapter Publisher feature. The `react-sortable-hoc` library, a
dependency used for drag-and-drop functionality, relies on the `findDOMNode` API. This
API has been completely removed in React 19. As a result, while the application will
build and load successfully, any attempt by an administrator to access the Chapter
Publisher will trigger a crash, rendering the feature completely non-functional.

sentry[bot]
sentry bot reviewed Feb 28, 2026
View reviewed changes
package.json
"@types/react-dom": "^19.0.0",
"@types/react-redux": "^7.1.24",
"@types/react-syntax-highlighter": "^15.5.7",
"@types/react-test-renderer": "^18.0.0",
Copy link

@sentry sentry bot Feb 28, 2026

Choose a reason for hiding this comment

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

Bug: The upgrade to react-test-renderer v19 removes the /shallow export, but TestUtils.ts still imports from it, which will cause the test suite to fail.
Severity: CRITICAL

Suggested Fix

To fix this, you can install react-shallow-renderer as a separate dependency and update the import statement in TestUtils.ts. Alternatively, refactor the tests to remove the usage of the shallow renderer and switch to a more modern testing 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#L147

Potential issue: The upgrade of `react-test-renderer` to version 19 introduces a
breaking change. React 19 removes the `react-test-renderer/shallow` export, which is
currently imported in `TestUtils.ts` via `import { createRenderer } from
'react-test-renderer/shallow';`. Because this module path no longer exists in the
updated package, any attempt to run the test suite will result in a runtime import
error, such as `Error: Cannot find module 'react-test-renderer/shallow'`. This will
cause the entire test suite to fail, as numerous test files depend on these utilities.

sentry[bot]
sentry bot reviewed Mar 1, 2026
View reviewed changes
package.json
"@types/react-dom": "^19.0.0",
"@types/react-redux": "^7.1.24",
"@types/react-syntax-highlighter": "^15.5.7",
"@types/react-test-renderer": "^18.0.0",
Copy link

@sentry sentry bot Mar 1, 2026

Choose a reason for hiding this comment

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

Bug: The upgrade to react-test-renderer v19 causes a runtime error because the code imports from react-test-renderer/shallow, an API that has been removed.
Severity: CRITICAL

Suggested Fix

The react-test-renderer/shallow export is deprecated. Add the react-shallow-renderer package as a new dev dependency. Then, update the import in src/commons/utils/TestUtils.ts to source createRenderer from the new react-shallow-renderer package. Also, update the @types/react-test-renderer dependency to match the major version of react-test-renderer.

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#L147

Potential issue: The `react-test-renderer` package was upgraded to v19, but the code was
not updated to reflect breaking changes in the new version. The file
`src/commons/utils/TestUtils.ts` imports `createRenderer` from
`react-test-renderer/shallow`, an export path that was completely removed in v19. This
will cause a runtime import error when tests are executed, leading to the failure of the
test suite. The issue is masked during compilation because the corresponding
`@types/react-test-renderer` package was not upgraded from v18.

sentry[bot]
sentry bot reviewed Mar 2, 2026
View reviewed changes
package.json
"react-dom": "^19.0.0",
"react-drag-drop-files": "^3.0.0",
"react-draggable": "^4.4.5",
"react-dropzone": "^15.0.0",
Copy link

@sentry sentry bot Mar 2, 2026

Choose a reason for hiding this comment

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

Bug: The react-konva package was not upgraded to a React 19 compatible version, while React itself was upgraded to v19. This will cause runtime errors.
Severity: CRITICAL

Suggested Fix

Upgrade the react-konva package in package.json from ^18.2.10 to a version compatible with React 19, such as ^19.0.0 or the latest available v19 release. Ensure the yarn.lock file is updated accordingly.

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#L86

Potential issue: The pull request upgrades `react` and `react-dom` from version 18 to 19
but leaves `react-konva` at version `^18.2.10`. The `react-konva` library depends on
React's internal APIs, and its major version must match React's major version to ensure
compatibility. This version mismatch will lead to runtime failures when components using
`react-konva` are rendered, as its v18 code is incompatible with React 19's internal
changes. This will break core visualization features like the CSE Machine and Data
Visualizer.

sentry[bot]
sentry bot reviewed Mar 2, 2026
View reviewed changes
package.json
"@types/react-dom": "^19.0.0",
"@types/react-redux": "^7.1.24",
"@types/react-syntax-highlighter": "^15.5.7",
"@types/react-test-renderer": "^18.0.0",
Copy link

@sentry sentry bot Mar 2, 2026

Choose a reason for hiding this comment

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

Bug: The upgrade of react-test-renderer to v19 removes the /shallow export, which is still used in the codebase. This will cause the entire test suite to fail.
Severity: CRITICAL

Suggested Fix

Replace the deprecated react-test-renderer/shallow import. Install the separate react-shallow-renderer package and update the import in src/commons/utils/TestUtils.ts to use it. Additionally, upgrade the @types/react-test-renderer package to match the version of react-test-renderer.

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#L147

Potential issue: The `react-test-renderer` package was upgraded to version 19, but its
`/shallow` export, which is used in `src/commons/utils/TestUtils.ts`, was removed in
this version. The type definitions package `@types/react-test-renderer` also remains at
an older version. When the test suite runs, the attempt to import from the non-existent
`react-test-renderer/shallow` path will cause a `MODULE_NOT_FOUND` error. This will
prevent any tests from running and cause the entire test suite to fail.

sentry[bot]
sentry bot reviewed Mar 2, 2026
View reviewed changes
package.json
"@types/react-dom": "^19.0.0",
"@types/react-redux": "^7.1.24",
"@types/react-syntax-highlighter": "^15.5.7",
"@types/react-test-renderer": "^18.0.0",
Copy link

@sentry sentry bot Mar 2, 2026

Choose a reason for hiding this comment

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

Bug: The upgrade to react-test-renderer v19 removes the react-test-renderer/shallow export, but the code still imports from it, which will cause a runtime error.
Severity: CRITICAL

Suggested Fix

Refactor the code in src/commons/utils/TestUtils.ts to no longer import from react-test-renderer/shallow, as this API was removed. An alternative shallow rendering approach compatible with React 19 should be used. Alternatively, revert the upgrade of react-test-renderer to a version below 19.

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#L147

Potential issue: The upgrade of `react-test-renderer` to v19.2.4 introduces a breaking
change. This version removes the `react-test-renderer/shallow` subpath export, which is
currently being imported in `src/commons/utils/TestUtils.ts`. Because this import path
no longer exists in the upgraded package, any attempt to run tests or execute code that
relies on `TestUtils.ts` will result in a module resolution error at runtime, causing a
crash and breaking the test suite.

sentry[bot]
sentry bot reviewed Mar 5, 2026
View reviewed changes
package.json
Comment on lines 77 to 86
"phaser": "~3.90.0",
"query-string": "^9.0.0",
"re-resizable": "^6.9.9",
"react": "^18.3.1",
"react": "^19.0.0",
"react-ace": "^14.0.0",
"react-debounce-render": "^8.0.2",
"react-dom": "^18.3.1",
"react-dom": "^19.0.0",
"react-drag-drop-files": "^3.0.0",
"react-draggable": "^4.4.5",
"react-dropzone": "^15.0.0",
Copy link

@sentry sentry bot Mar 5, 2026

Choose a reason for hiding this comment

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

Bug: The react-sortable-hoc library is incompatible with React 19 because it uses the removed findDOMNode API, which will cause a runtime crash in the Chapter Publisher feature.
Severity: CRITICAL

Suggested Fix

Replace the unmaintained react-sortable-hoc library. The library's maintainers recommend migrating to a modern drag-and-drop solution like @dnd-kit to ensure compatibility with React 19 and future versions.

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#L77-L86

Potential issue: The upgrade to React 19 introduces an incompatibility with the
`react-sortable-hoc` library, which is no longer maintained. This library depends on
`ReactDOM.findDOMNode`, an API that was completely removed in React 19. As a result, any
component using this library, such as `SortableList` in the Chapter Publisher feature,
will trigger a `TypeError: ReactDOM.findDOMNode is not a function` runtime error upon
rendering. This will cause the Chapter Publisher admin feature to crash, blocking staff
from managing chapter files.

package.json
Comment on lines 139 to 147
"@types/js-cookie": "^3.0.6",
"@types/js-yaml": "^4.0.5",
"@types/lodash": "^4.14.195",
"@types/react": "^18.3.3",
"@types/react": "^19.0.0",
"@types/react-copy-to-clipboard": "^5.0.4",
"@types/react-dom": "^18.3.0",
"@types/react-dom": "^19.0.0",
"@types/react-redux": "^7.1.24",
"@types/react-syntax-highlighter": "^15.5.7",
"@types/react-test-renderer": "^18.0.0",
Copy link

@sentry sentry bot Mar 5, 2026

Choose a reason for hiding this comment

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

Bug: The test utility shallowRender imports from react-test-renderer/shallow, a path that was removed in React 19. This will cause the test suite to fail.
Severity: CRITICAL

Suggested Fix

To resolve the test failures, either install the react-shallow-renderer package directly and update the import path in TestUtils.ts, or migrate the affected tests from shallow rendering to use a more modern library like @testing-library/react.

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#L139-L147

Potential issue: The upgrade to React 19 removes the `react-test-renderer/shallow`
subpath export. The codebase contains a `shallowRender` test utility that imports
`createRenderer` from this path. Since the export no longer exists in
`react-test-renderer@^19.0.0` and the `react-shallow-renderer` package has been removed
from dependencies, any test file that uses the `shallowRender` function will fail with a
module import error. This will prevent the test suite from running successfully.

sentry[bot]
sentry bot reviewed Mar 5, 2026
View reviewed changes
package.json
Comment on lines 139 to 147
"@types/js-cookie": "^3.0.6",
"@types/js-yaml": "^4.0.5",
"@types/lodash": "^4.14.195",
"@types/react": "^18.3.3",
"@types/react": "^19.0.0",
"@types/react-copy-to-clipboard": "^5.0.4",
"@types/react-dom": "^18.3.0",
"@types/react-dom": "^19.0.0",
"@types/react-redux": "^7.1.24",
"@types/react-syntax-highlighter": "^15.5.7",
"@types/react-test-renderer": "^18.0.0",
Copy link

@sentry sentry bot Mar 5, 2026

Choose a reason for hiding this comment

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

Bug: react-draggable v4 is used without the nodeRef prop in MobileKeyboard.tsx and DraggableRepl.tsx. This will crash in React 19, which removes the findDOMNode fallback.
Severity: CRITICAL

Suggested Fix

Add the nodeRef prop to all <Draggable> components, as demonstrated in Chatbot.tsx. This involves creating a React.useRef, passing it to the nodeRef prop of <Draggable>, and attaching it as a ref to the underlying draggable DOM element.

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#L139-L147

Potential issue: The upgrade to React 19 removes `ReactDOM.findDOMNode`. The
`react-draggable` library (v4.4.5) relies on this function as a fallback when the
`nodeRef` prop is not provided. The components `MobileKeyboard.tsx` and
`DraggableRepl.tsx` use `<Draggable>` without `nodeRef`, which will cause a runtime
crash when users on mobile devices attempt to drag the keyboard or the REPL panel. This
breaks core functionality for mobile users.

package.json
Comment on lines 77 to 86
"phaser": "~3.90.0",
"query-string": "^9.0.0",
"re-resizable": "^6.9.9",
"react": "^18.3.1",
"react": "^19.0.0",
"react-ace": "^14.0.0",
"react-debounce-render": "^8.0.2",
"react-dom": "^18.3.1",
"react-dom": "^19.0.0",
"react-drag-drop-files": "^3.0.0",
"react-draggable": "^4.4.5",
"react-dropzone": "^15.0.0",
Copy link

@sentry sentry bot Mar 5, 2026

Choose a reason for hiding this comment

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

Bug: react-sortable-hoc v2.0.0 is incompatible with React 19 as it relies on findDOMNode. This will cause crashes when reordering items in the Chapter Publisher.
Severity: CRITICAL

Suggested Fix

Replace the unmaintained react-sortable-hoc library with a modern, compatible alternative like @dnd-kit, as recommended by the original library authors. This will require refactoring the SortableList component and its usage in ChapterPublisherEditor.tsx.

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#L77-L86

Potential issue: The upgrade to React 19 is incompatible with `react-sortable-hoc`
v2.0.0, which is not being updated in this PR. The library's architecture depends on
`ReactDOM.findDOMNode`, a function that is completely removed in React 19. This will
cause a runtime crash when users interact with the drag-and-drop functionality in the
`ChapterPublisherEditor` component, specifically when trying to reorder chapter files.

sentry[bot]
sentry bot reviewed Mar 9, 2026
View reviewed changes
package.json
"@types/react-dom": "^19.0.0",
"@types/react-redux": "^7.1.24",
"@types/react-syntax-highlighter": "^15.5.7",
"@types/react-test-renderer": "^18.0.0",
Copy link

@sentry sentry bot Mar 9, 2026

Choose a reason for hiding this comment

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

Bug: The upgrade of react-test-renderer to v19 breaks the import of createRenderer from react-test-renderer/shallow, as this export was removed. This will cause test suites to fail.
Severity: CRITICAL

Suggested Fix

To fix the broken import, install the react-shallow-renderer package and update the import in src/commons/utils/TestUtils.ts to import { createRenderer } from 'react-shallow-renderer';. Additionally, update the @types/react-test-renderer package to match version 19.

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#L147

Potential issue: The `react-test-renderer` package was upgraded to version 19, but the
code in `src/commons/utils/TestUtils.ts` still attempts to import `createRenderer` from
the `react-test-renderer/shallow` path. This export was removed in version 19 of the
package; the shallow renderer is now available in a separate `react-shallow-renderer`
package. This will cause a runtime import failure when the test suite runs, breaking all
tests that depend on the `shallowRender` utility and preventing CI checks from passing.

sentry[bot]
sentry bot reviewed Mar 9, 2026
View reviewed changes
package.json
"process": "^0.11.10",
"react-error-overlay": "^6.0.11",
"react-test-renderer": "^18.2.0",
"react-test-renderer": "^19.0.0",
Copy link

@sentry sentry bot Mar 9, 2026

Choose a reason for hiding this comment

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

Bug: The code imports from react-test-renderer/shallow, a path that was removed in React 19. This will cause all dependent tests to fail at module load time.
Severity: CRITICAL

Suggested Fix

Since the shallow renderer was removed in React 19, all usages of it should be migrated. Replace the shallow rendering logic in TestUtils.ts and dependent tests with an alternative, such as using ReactTestRenderer.create() from the main react-test-renderer package or migrating to React Testing 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#L176

Potential issue: The upgrade to `react-test-renderer@19` introduces a breaking change.
The code in `src/commons/utils/TestUtils.ts` imports `createRenderer` from
`react-test-renderer/shallow`. This module path was completely removed in React 19. As a
result, numerous test files (over 30) that depend on `TestUtils.ts` will fail with a
module import error when the test suite is executed. This is a load-time error that will
prevent the tests from running, rather than a type mismatch issue.

sentry[bot]
sentry bot reviewed Mar 9, 2026
View reviewed changes
package.json
Comment on lines +80 to +83
"react": "^19.0.0",
"react-ace": "^14.0.0",
"react-debounce-render": "^8.0.2",
"react-dom": "^18.3.1",
"react-dom": "^19.0.0",
Copy link

@sentry sentry bot Mar 9, 2026

Choose a reason for hiding this comment

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

Bug: DraggableRepl.tsx and MobileKeyboard.tsx use <Draggable> without the required nodeRef prop. This will cause a runtime crash in React 19, which removes the findDOMNode fallback.
Severity: HIGH

Suggested Fix

In DraggableRepl.tsx and MobileKeyboard.tsx, create a React.useRef for the draggable element and pass it to the <Draggable> component via the nodeRef prop. This will prevent react-draggable from attempting to use the now-removed findDOMNode API.

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#L80-L83

Potential issue: The upgrade to React 19 removes `ReactDOM.findDOMNode`, which the
`react-draggable` library uses as a fallback when a `nodeRef` prop is not provided. The
components in `DraggableRepl.tsx` and `MobileKeyboard.tsx` use the `<Draggable>`
component without this required `nodeRef` prop. As a result, any user attempt to drag
these UI elements will cause a runtime crash. The `Chatbot.tsx` component correctly
implements this pattern, indicating an oversight in the other two files.

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

Reviewers

1 more reviewer

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

Reviewers whose approvals may not affect merge requirements

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

dependencies This pull request updates dependency files

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants