2f86fbab81
Runtime prefetching relies on the presence of headers to determine caching behavior: `x-nextjs-postponed` indicates if the response was partial (so it knows if it should trigger a dynamic request to retrieve the missing data), and `x-nextjs-stale-time` provided stale time information to the client router. This worked fine in `next start` but due to how this is modeled in our Vercel deployment adapter, it was not possible to set runtime headers after the initial headers have been sent, as these requests were routed to prerenders. As a result of this limitation, this moves both the isPartial flag and the stale time value into the payload body. The response is run through a transform stream that replaces a sentinel value (`"rp": [sentinel]`) with the final stale time/isPartial values after we determine them. This avoids regenerating the entire RSC payload while ensuring correct values are sent to the client. Both properties are only included in runtime prefetch responses. Closes NAR-494 --------- Co-authored-by: Josh Story <[email protected]>
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 [email protected]. We will add you to the program and provide further instructions for submitting your report.