JosephandGitHub
54ac71cdb8
- Questions kept coming up about where `use cache` results actually live, and how static shells, App Shells, and ISR relate - the answers were spread across several pages, but not tied together on the getting-started guide - The runtime prefetching example also implied cookie data needs `allow-runtime`, when the App Shell already carries session data - `allow-runtime` is really about URL data. **Changes** (`docs/app/getting-started/caching`) - Reworked the Usage intro to lead with the cache lifetime concept and hand off to Prerendering - Added a **Where cached content is stored** section: server cache, remote handler, and browser, framed around a cached result being a serialized payload that travels to each. - > if I had time to make it shorter, I would... - We will most likely have a visual aid there and trim it down - Added a static shell ↔ App Shell explanation in Prerendering, and a short Incremental Static Regeneration pointer to the ISR guide - Corrected the runtime prefetching section to the URL-data model (`searchParams`/`params`) - replaced the cookie example with a `/search` one that actually needs `allow-runtime`. - `catchError` (stabilized). - Cross-linked `stale`/`revalidate`/`expire` to `cacheLife` - reviewed and fixed the code-block highlights.
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.