Pages router: Enable strict next/head children reconciler by default
#65418
Conversation
eps1lon
force-pushed
the
sebbie/enable-new-head-reconciler
branch
from
532b7be
to
f239d24
Compare
eps1lon
requested review from
timneutkens,
ijjk,
shuding,
huozhi,
ztanner,
feedthejim,
a team and
wyattjoh
as code owners
| /** @default true */ | ||
| strictNextHead?: boolean |
There was a problem hiding this comment.
Since this was experimental I think we can remove it, unless there's still a valid case for disabling?
There was a problem hiding this comment.
@timneutkens mentioned that some people may complain for SEO reasons even though extra attributes do not affect it. At least that's what happened in the past he said.
If this comes up, and people don't provide evidence that strictNextHead: true is bad, we can offer strictNextHead: false as an escape hatch. Client-side updates to next/head children would be broken but at least it would fix their imagined SEO issues.
But practically, I want to remove this soon after Next.js 15 is out stable. vercel/front is running with strictNextHead for a while by that time so it should've had sufficient soak-time.
Enables the new
hext/headchildren reconciler introduced in #65408 by default.The non-strict one is not compatible with React 19. To opt-out, explicitly set
experimental.strictNextHeadtofalse.undefinedornullwill still enable the new reconciler.Closes NEXT-3330