Andrew ClarkandGitHub
5c27d82bfb
Under Cache Components, a `<Link prefetch={true}>` pointing at a route
that hasn't enabled Partial Prefetching quietly falls back to a legacy
full prefetch: it pulls down the route's dynamic data instead of just
the static shell, defeating the static/dynamic split. In development we
now surface this with a console error that explains the fallback and
points at how to opt in — app-wide with `partialPrefetching`, or
per-route with `prefetch = 'partial'`.
The check runs when the navigation happens, not when the link is
prefetched. Dev doesn't prefetch, so navigation is the only point where
both the originating link's fetch strategy and the resolved route tree
are in hand; it also means an app that has just turned on Cache
Components isn't flooded with warnings for every `prefetch={true}` link
on the page, since you only hear about a route when you actually
navigate to it. The decision reads a single hint at the root of the
resolved route tree that records whether any segment in the route opted
into Partial Prefetching.
Scope: the warning fires on every qualifying navigation, including ones
to fully static routes where a full prefetch costs nothing. Suppressing
it for fully-static targets is deferred — the route-level "has dynamic
data" signal isn't cheaply available on cache-served repeat navigations.
<!-- NEXT_JS_LLM_PR -->
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.