Skip to content

Update react monorepo (major) - #9

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

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

Conversation

@renovate

@renovate renovate Bot commented Mar 24, 2021 •
edited
Loading

Copy link
Copy Markdown

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
eslint-plugin-react-hooks (source) 1.7.0 → 7.1.1 age confidence
react (source) 17.0.2 → 19.2.8 age confidence
react-dom (source) 17.0.2 → 19.2.8 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

v4.6.2

Compare Source

v4.6.1

Compare Source

v4.6.0

v4.5.0

v4.4.0

  • No changes, this was an automated release together with React 18.

v4.3.0

v4.2.0

  • No changes, this was an automated release together with React 17.

v4.1.2

v4.1.1

v4.1.0

v4.0.8

v4.0.7

v4.0.6

v4.0.5

v4.0.4

v4.0.3

  • Remove the heuristic that checks all Hooks ending with Effect due to too many false positives. (@​gaearon in #​19004)

v4.0.2

v4.0.1

v4.0.0

v3.0.0

v2.5.0

v2.4.0

v2.0.0

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

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • 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 force-pushed the renovate/major-react-monorepo branch from bf7c768 to 82e72ee Compare March 30, 2021 05:57
@renovate renovate Bot changed the title Update dependency eslint-plugin-react-hooks to v4 Update dependency eslint-plugin-react-hooks to v4 - autoclosed May 4, 2021
@renovate renovate Bot closed this May 4, 2021
@renovate
renovate Bot deleted the renovate/major-react-monorepo branch May 4, 2021 03:29
@renovate renovate Bot changed the title Update dependency eslint-plugin-react-hooks to v4 - autoclosed Update dependency eslint-plugin-react-hooks to v4 May 4, 2021
@renovate renovate Bot reopened this May 4, 2021
@renovate
renovate Bot restored the renovate/major-react-monorepo branch May 4, 2021 04:44
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from 82e72ee to a4bfcf2 Compare May 4, 2021 04:46
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from a4bfcf2 to 0f3cad2 Compare March 7, 2022 17:54
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from 0f3cad2 to d19d622 Compare April 24, 2022 22:54
@renovate renovate Bot changed the title Update dependency eslint-plugin-react-hooks to v4 Update react monorepo (major) Apr 24, 2022
@renovate

renovate Bot commented Apr 24, 2022 •
edited
Loading

Copy link
Copy Markdown
Author

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @next/react-dev-overlay@10.1.1
npm WARN Found: react@18.3.1
npm WARN node_modules/react
npm WARN   dev react@"18.3.1" from the root project
npm WARN   1 more (react-dom)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.9.0 || ^17" from @next/react-dev-overlay@10.1.1
npm WARN node_modules/@next/react-dev-overlay
npm WARN   @next/react-dev-overlay@"10.1.1" from next@10.1.1
npm WARN   node_modules/next
npm WARN 
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN   peer react@"^16.9.0 || ^17" from @next/react-dev-overlay@10.1.1
npm WARN   node_modules/@next/react-dev-overlay
npm WARN     @next/react-dev-overlay@"10.1.1" from next@10.1.1
npm WARN     node_modules/next
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @next/react-dev-overlay@10.1.1
npm WARN Found: react-dom@18.3.1
npm WARN node_modules/react-dom
npm WARN   dev react-dom@"18.3.1" from the root project
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react-dom@"^16.9.0 || ^17" from @next/react-dev-overlay@10.1.1
npm WARN node_modules/@next/react-dev-overlay
npm WARN   @next/react-dev-overlay@"10.1.1" from next@10.1.1
npm WARN   node_modules/next
npm WARN 
npm WARN Conflicting peer dependency: react-dom@17.0.2
npm WARN node_modules/react-dom
npm WARN   peer react-dom@"^16.9.0 || ^17" from @next/react-dev-overlay@10.1.1
npm WARN   node_modules/@next/react-dev-overlay
npm WARN     @next/react-dev-overlay@"10.1.1" from next@10.1.1
npm WARN     node_modules/next
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: next@10.1.1
npm ERR! Found: react@18.3.1
npm ERR! node_modules/react
npm ERR!   dev react@"18.3.1" from the root project
npm ERR!   peer react@"^18.3.1" from react-dom@18.3.1
npm ERR!   node_modules/react-dom
npm ERR!     dev react-dom@"18.3.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.6.0 || ^17" from next@10.1.1
npm ERR! node_modules/next
npm ERR!   dev next@"10.1.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: react@17.0.2
npm ERR! node_modules/react
npm ERR!   peer react@"^16.6.0 || ^17" from next@10.1.1
npm ERR!   node_modules/next
npm ERR!     dev next@"10.1.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-04-26T18_02_31_512Z-debug-0.log

@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from d19d622 to 02cbf94 Compare May 15, 2022 23:16
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from 02cbf94 to 9f6ef3c Compare June 18, 2022 22:00
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 6b134cb to 90fbfdd Compare April 26, 2024 18:02
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from 90fbfdd to d721f27 Compare October 11, 2024 16:16
@renovate

renovate Bot commented Oct 11, 2024 •
edited
Loading

Copy link
Copy Markdown
Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @next/react-dev-overlay@10.1.1
npm WARN Found: react@19.2.8
npm WARN node_modules/react
npm WARN   dev react@"19.2.8" from the root project
npm WARN   1 more (react-dom)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.9.0 || ^17" from @next/react-dev-overlay@10.1.1
npm WARN node_modules/@next/react-dev-overlay
npm WARN   @next/react-dev-overlay@"10.1.1" from next@10.1.1
npm WARN   node_modules/next
npm WARN 
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN   peer react@"^16.9.0 || ^17" from @next/react-dev-overlay@10.1.1
npm WARN   node_modules/@next/react-dev-overlay
npm WARN     @next/react-dev-overlay@"10.1.1" from next@10.1.1
npm WARN     node_modules/next
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @next/react-dev-overlay@10.1.1
npm WARN Found: react-dom@19.2.8
npm WARN node_modules/react-dom
npm WARN   dev react-dom@"19.2.8" from the root project
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react-dom@"^16.9.0 || ^17" from @next/react-dev-overlay@10.1.1
npm WARN node_modules/@next/react-dev-overlay
npm WARN   @next/react-dev-overlay@"10.1.1" from next@10.1.1
npm WARN   node_modules/next
npm WARN 
npm WARN Conflicting peer dependency: react-dom@17.0.2
npm WARN node_modules/react-dom
npm WARN   peer react-dom@"^16.9.0 || ^17" from @next/react-dev-overlay@10.1.1
npm WARN   node_modules/@next/react-dev-overlay
npm WARN     @next/react-dev-overlay@"10.1.1" from next@10.1.1
npm WARN     node_modules/next
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: next@10.1.1
npm ERR! Found: react@19.2.8
npm ERR! node_modules/react
npm ERR!   dev react@"19.2.8" from the root project
npm ERR!   peer react@"^19.2.8" from react-dom@19.2.8
npm ERR!   node_modules/react-dom
npm ERR!     dev react-dom@"19.2.8" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.6.0 || ^17" from next@10.1.1
npm ERR! node_modules/next
npm ERR!   dev next@"10.1.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: react@17.0.2
npm ERR! node_modules/react
npm ERR!   peer react@"^16.6.0 || ^17" from next@10.1.1
npm ERR!   node_modules/next
npm ERR!     dev next@"10.1.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-08-12T04_31_55_028Z-debug-0.log

@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from d721f27 to a70cb03 Compare December 5, 2024 19:21
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from a70cb03 to 6889ab7 Compare February 28, 2025 16:03
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from 6889ab7 to d94aa00 Compare March 28, 2025 22:41
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from d94aa00 to 3a50639 Compare August 3, 2025 23:09
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 83712d0 to 6b33dc4 Compare October 10, 2025 19:58
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from 6b33dc4 to 30a950e Compare November 22, 2025 08:06
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from 30a950e to 14aacaa Compare December 3, 2025 17:51
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 13e48a3 to 323fa61 Compare December 14, 2025 11:28
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from 323fa61 to 387c06a Compare January 26, 2026 21:02
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from 387c06a to dea1654 Compare April 9, 2026 00:13
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from dea1654 to da4c0b8 Compare April 19, 2026 04:10
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from da4c0b8 to 785fed0 Compare May 6, 2026 18:11
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from 785fed0 to c3f815f Compare July 26, 2026 01:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

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