You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
React is removing Server Context (it was never documented) and Next never fully implemented it anyway. This removes any references to server context APIs (entirely internal) which is now required since the latest React canary no longer exposes these APIs.
* Server Context is specifically only available in Server Components.
530
-
* It has to hold values that can't change while rendering from the common layout down.
531
-
* An example of this would be that `headers` are available but `searchParams` are not because that'd mean we have to render from the root layout down on all requests.
532
-
*/
533
-
constserverContexts: Array<[string,any]>=[
534
-
['WORKAROUND',null],// TODO-APP: First value has a bug currently where the value is not set on the second request: https://github.com/facebook/react/issues/24849
535
-
]
536
-
537
526
/**
538
527
* Dynamic parameters. E.g. when you visit `/dashboard/vercel` which is rendered by `/dashboard/[slug]` the value will be {"slug": "vercel"}.
539
528
*/
@@ -561,7 +550,6 @@ async function renderToHTMLOrFlightImpl(
561
550
assetPrefix,
562
551
flightDataRendererErrorHandler,
563
552
serverComponentsErrorHandler,
564
-
serverContexts,
565
553
isNotFoundPath,
566
554
res,
567
555
}
@@ -580,7 +568,6 @@ async function renderToHTMLOrFlightImpl(
0 commit comments