Andrew Clark
04b8a9d218
The head (metadata) is already fetched and cached like a page segment, keyed at its own metadata vary path, but the render tree stored it as two extra fields on the page node's CacheNode. Every navigation function threaded the seed head and the metadata vary path down to every child so the page node could resolve it, using a copy of the segment resolution logic that only ran for pages, and the BFCache faked a head-only entry by writing the head into a segment entry's rsc slot. Store the head as an ordinary CacheNode instead, on a one-node route tree kept beside the route's render tree. A new RootRouteTree type names this pair: it is what a server response decodes to, what the router state holds, and what a navigation produces. The head node is created by the same createRenderTreeForSegment as page segments, so the BFCache, hydration, history traversal, cache read and deferred-data paths apply to it unchanged, and startPPRNavigation returns the tree and head tasks together. The Head component reads the node directly, so findHeadInCache is gone. The head is reused on the same terms as the page it belongs to: an unchanged vary path and not a same-page navigation. When every segment is cached but the head is not, the navigation sends the server's metadata-only request instead of refetching the page and discarding it, and a response that carries no head is treated as a mismatch like a missing segment. The head's BFCache entry also has its stale time updated from dynamic responses, which never happened before.
Next.js
Getting Started
Used by some of the world's largest companies, Next.js enables you to create full-stack web applications by extending the latest React features, and integrating powerful Rust-based JavaScript tooling for the fastest builds.
- Visit our Learn Next.js course to get started with Next.js.
- Visit the Next.js Showcase to see more sites built with Next.js.
Documentation
Visit https://nextjs.org/docs to view the full documentation.
Community
The Next.js community can be found on GitHub Discussions where you can ask questions, voice ideas, and share your projects with other people.
To chat with other community members, you can join the Next.js Discord server.
Do note that our Code of Conduct applies to all Next.js community channels. Users are highly encouraged to read and adhere to it to avoid repercussions.
Contributing
Contributions to Next.js are welcome and highly appreciated. However, before you jump right into it, we would like you to review our Contribution Guidelines to make sure you have a smooth experience contributing to Next.js.
Good First Issues:
We have a list of good first issues that contain bugs that have a relatively limited scope. This is a great place for newcomers and beginners alike to get started, gain experience, and get familiar with our contribution process.
Security
If you believe you have found a security vulnerability in Next.js, we encourage you to responsibly disclose this and NOT open a public issue.
To participate in our Open Source Software Bug Bounty program, please email responsible.disclosure@vercel.com. We will add you to the program and provide further instructions for submitting your report.