f7d262902a
Next.js relies on on the Resume Data Cache to prevent tearing between the statically prefetchable parts of the UI by seeding the resume with the same cache as the revalidation/build. The RDC data is stashed in the postponed state which is attached to all of the different outputs that comprise a page (the segments, the HTML, and the dynamic RSC data). However, when deployed to targets like Vercel, the revalidation was incorrectly bypassing the cache for the RSC entry, because it thought that it was a resume. This led to a drift in cached values, because the revalidation would cause the main RSC entries RDC data to contain a different value than what was used for the segment prefetches & HTML ISR entry. Fixes NAR-493 Co-authored-by: JJ Kasper <[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.