Issue Station
Sign In
Tools hereToolbox

nextjs - ✅(Solved) Fix Next 16 Portals does not replace contents with cacheComponents [7 pull requests, 7 comments, 4 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#85279•Fetched 2026-04-08 02:16:37
View on GitHub
Comments
7
Participants
4
Timeline
22
Reactions
0
Author
khuezykhuezy
Participants
ceolinwillceolinwillgithub-actions[bot]github-actions[bot]icyJosephicyJosephkhuezykhuezy
Timeline (top)
commented ×7subscribed ×7cross-referenced ×2closed ×1

Fix Action

Fixed

PR fix notes

PR #85980: Upgrade React from fa50caf5-20251107 to 52684925-20251110

Description (problem / solution / changelog)

Closes https://github.com/vercel/next.js/issues/85279 Closes https://github.com/vercel/next.js/issues/85390

diff facebook/[email protected]

<details> <summary>React upstream changes</summary> </details>

Changed files

  • package.json (modified, +16/-16)
  • packages/next/src/compiled/react-dom-experimental/cjs/react-dom-client.development.js (modified, +328/-310)
  • packages/next/src/compiled/react-dom-experimental/cjs/react-dom-client.production.js (modified, +353/-335)
  • packages/next/src/compiled/react-dom-experimental/cjs/react-dom-profiling.development.js (modified, +328/-310)
  • packages/next/src/compiled/react-dom-experimental/cjs/react-dom-profiling.profiling.js (modified, +358/-340)
  • packages/next/src/compiled/react-dom-experimental/cjs/react-dom-server-legacy.browser.development.js (modified, +32/-35)
  • packages/next/src/compiled/react-dom-experimental/cjs/react-dom-server-legacy.browser.production.js (modified, +32/-37)
  • packages/next/src/compiled/react-dom-experimental/cjs/react-dom-server-legacy.node.development.js (modified, +32/-35)
  • packages/next/src/compiled/react-dom-experimental/cjs/react-dom-server-legacy.node.production.js (modified, +32/-37)
  • packages/next/src/compiled/react-dom-experimental/cjs/react-dom-server.browser.development.js (modified, +46/-63)
  • packages/next/src/compiled/react-dom-experimental/cjs/react-dom-server.browser.production.js (modified, +46/-65)
  • packages/next/src/compiled/react-dom-experimental/cjs/react-dom-server.bun.production.js (modified, +46/-65)
  • packages/next/src/compiled/react-dom-experimental/cjs/react-dom-server.edge.development.js (modified, +46/-63)
  • packages/next/src/compiled/react-dom-experimental/cjs/react-dom-server.edge.production.js (modified, +46/-65)
  • packages/next/src/compiled/react-dom-experimental/cjs/react-dom-server.node.development.js (modified, +46/-63)
  • packages/next/src/compiled/react-dom-experimental/cjs/react-dom-server.node.production.js (modified, +46/-65)
  • packages/next/src/compiled/react-dom-experimental/cjs/react-dom-unstable_testing.development.js (modified, +328/-310)
  • packages/next/src/compiled/react-dom-experimental/cjs/react-dom-unstable_testing.production.js (modified, +353/-335)
  • packages/next/src/compiled/react-dom-experimental/cjs/react-dom.development.js (modified, +1/-1)
  • packages/next/src/compiled/react-dom-experimental/cjs/react-dom.production.js (modified, +1/-1)
  • packages/next/src/compiled/react-dom-experimental/cjs/react-dom.react-server.development.js (modified, +1/-1)
  • packages/next/src/compiled/react-dom-experimental/cjs/react-dom.react-server.production.js (modified, +1/-1)
  • packages/next/src/compiled/react-dom-experimental/package.json (modified, +2/-2)
  • packages/next/src/compiled/react-dom/cjs/react-dom-client.development.js (modified, +327/-309)
  • packages/next/src/compiled/react-dom/cjs/react-dom-client.production.js (modified, +349/-331)
  • packages/next/src/compiled/react-dom/cjs/react-dom-profiling.development.js (modified, +327/-309)
  • packages/next/src/compiled/react-dom/cjs/react-dom-profiling.profiling.js (modified, +372/-354)
  • packages/next/src/compiled/react-dom/cjs/react-dom-server-legacy.browser.development.js (modified, +42/-39)
  • packages/next/src/compiled/react-dom/cjs/react-dom-server-legacy.browser.production.js (modified, +44/-39)
  • packages/next/src/compiled/react-dom/cjs/react-dom-server-legacy.node.development.js (modified, +42/-39)
  • packages/next/src/compiled/react-dom/cjs/react-dom-server-legacy.node.production.js (modified, +44/-39)
  • packages/next/src/compiled/react-dom/cjs/react-dom-server.browser.development.js (modified, +50/-61)
  • packages/next/src/compiled/react-dom/cjs/react-dom-server.browser.production.js (modified, +52/-61)
  • packages/next/src/compiled/react-dom/cjs/react-dom-server.bun.production.js (modified, +52/-61)
  • packages/next/src/compiled/react-dom/cjs/react-dom-server.edge.development.js (modified, +50/-61)
  • packages/next/src/compiled/react-dom/cjs/react-dom-server.edge.production.js (modified, +52/-61)
  • packages/next/src/compiled/react-dom/cjs/react-dom-server.node.development.js (modified, +50/-61)
  • packages/next/src/compiled/react-dom/cjs/react-dom-server.node.production.js (modified, +52/-61)
  • packages/next/src/compiled/react-dom/cjs/react-dom.development.js (modified, +1/-1)
  • packages/next/src/compiled/react-dom/cjs/react-dom.production.js (modified, +1/-1)
  • packages/next/src/compiled/react-dom/cjs/react-dom.react-server.development.js (modified, +1/-1)
  • packages/next/src/compiled/react-dom/cjs/react-dom.react-server.production.js (modified, +1/-1)
  • packages/next/src/compiled/react-dom/package.json (modified, +2/-2)
  • packages/next/src/compiled/react-experimental/cjs/react.development.js (modified, +1/-1)
  • packages/next/src/compiled/react-experimental/cjs/react.production.js (modified, +1/-1)
  • packages/next/src/compiled/react-experimental/cjs/react.react-server.development.js (modified, +1/-1)
  • packages/next/src/compiled/react-experimental/cjs/react.react-server.production.js (modified, +1/-1)
  • packages/next/src/compiled/react-is/package.json (modified, +1/-1)
  • packages/next/src/compiled/react-server-dom-turbopack-experimental/cjs/react-server-dom-turbopack-client.browser.development.js (modified, +2/-2)
  • packages/next/src/compiled/react-server-dom-turbopack-experimental/package.json (modified, +2/-2)
  • packages/next/src/compiled/react-server-dom-turbopack/cjs/react-server-dom-turbopack-client.browser.development.js (modified, +2/-2)
  • packages/next/src/compiled/react-server-dom-turbopack/package.json (modified, +2/-2)
  • packages/next/src/compiled/react-server-dom-webpack-experimental/cjs/react-server-dom-webpack-client.browser.development.js (modified, +2/-2)
  • packages/next/src/compiled/react-server-dom-webpack-experimental/package.json (modified, +2/-2)
  • packages/next/src/compiled/react-server-dom-webpack/cjs/react-server-dom-webpack-client.browser.development.js (modified, +2/-2)
  • packages/next/src/compiled/react-server-dom-webpack/package.json (modified, +2/-2)
  • packages/next/src/compiled/react/cjs/react.development.js (modified, +1/-1)
  • packages/next/src/compiled/react/cjs/react.production.js (modified, +1/-1)
  • packages/next/src/compiled/react/cjs/react.react-server.development.js (modified, +1/-1)
  • packages/next/src/compiled/react/cjs/react.react-server.production.js (modified, +1/-1)
  • packages/next/src/compiled/unistore/unistore.js (modified, +1/-1)
  • pnpm-lock.yaml (modified, +583/-548)

Code Example

N/A
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://github.com/khuezy/next16-portalbug

To Reproduce

Repro steps are in the README of the link above.

  1. npm run dev
  2. go to localhost:3000
  3. Click on 'a', see the portal at the top
  4. Click on 'b', see the portal at the top, it does not replace A's portal.

Current vs. Expected behavior

When using React Portals, I expect the contents of the portal to be replaced with the new content. This works on Next 15 and below but is broken in Next 16

Provide environment information

N/A

Which area(s) are affected? (Select all that apply)

cacheComponents

Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local)

Additional context

No response

extent analysis

TL;DR

The issue with React Portals not replacing content in Next 16 can be addressed by investigating the changes in Next 16's rendering mechanism and adjusting the portal implementation accordingly.

Guidance

  • Review the Next 16 documentation and release notes to understand changes in rendering and portal support.
  • Investigate the cacheComponents area, as it is marked as affected, and verify if caching is interfering with portal updates.
  • Check the portal implementation in the provided GitHub repository and compare it with Next

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#model compatibility#GPU setup#container setup#orchestration issue#cache issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING