--- title: Next.js 16.3 rewrites prefetching, vibe-coded landing... description: Next.js 16.3 ships Instant Navigations and Partial Prefetching, changing how caching works for anyone on the App Router. A self-hosted Next.js 16 writeup... canonical: https://daily.dev/posts/next-js-16-3-rewrites-prefetching-vibe-coded-landing-pages-become-a-red-flag-hurvwwupw twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Next.js 16.3 rewrites prefetching, vibe-coded landing pages become a red flag | daily.dev og:description: Next.js 16.3 ships Instant Navigations and Partial Prefetching, changing how caching works for anyone on the App Router. A self-hosted Next.js 16 writeup... og:url: https://daily.dev/posts/next-js-16-3-rewrites-prefetching-vibe-coded-landing-pages-become-a-red-flag-hurvwwupw og:image: https://api.daily.dev/og/posts/HUrvwwUPw.png og:image:alt: Next.js 16.3 rewrites prefetching, vibe-coded landing pages become a red flag og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Next.js 16.3 rewrites prefetching, vibe-coded landing pages become a red flag **[Web Digest](https://daily.dev/sources/webdev_digest)** · 4 min read · 0 upvotes · 0 comments ## Summary Next.js 16.3 ships Instant Navigations and Partial Prefetching, changing how caching works for anyone on the App Router. A self-hosted Next.js 16 writeup separately tackles the Redis cache-handler problem for multi-container 'use cache' deployments. Developers are publicly turning on the AI-generated landing page aesthetic, with Mitchell Hashimoto and Koen Bok leading the pile-on. A deep dive on scraping the same URL through six different layers shows LLMs and crawlers see very different versions of your pages. ## Content **TLDR:** Next.js 16.3 ships Instant Navigations and Partial Prefetching, changing how caching works for anyone on the App Router. A self-hosted Next.js 16 writeup separately tackles the Redis cache-handler problem for multi-container 'use cache' deployments. Developers are publicly turning on the AI-generated landing page aesthetic, with Mitchell Hashimoto and Koen Bok leading the pile-on. A deep dive on scraping the same URL through six different layers shows LLMs and crawlers see very different versions of your pages. --- ## Next.js 16.3 changes prefetching and caching behind two new flags Instead of prefetching the full RSC payload per URL, Next.js now prefetches a shared App Shell per route pattern (like /chat/[id]) and only fetches URL-specific data when prefetch={true} is set on a Link. This lands behind the cacheComponents and partialPrefetching flags, alongside 'use cache', cacheLife(), and a React Activity-based approach that preserves DOM/state for recently visited screens instead of unmounting them. If you're running Cloudflare OpenNext, note there are current support gaps for these features. [Read more](https://daily.dev/posts/FlTk0KHyB) ## Self-hosted Next.js 16 'use cache' breaks across containers without a shared Redis handler The new 'use cache' directive stores data in per-process memory, so every container in a multi-container deployment ends up with its own cache, and revalidateTag only clears one of them. The fix is a custom Redis-backed handler using the plural cacheHandlers config (not the older singular cacheHandler for ISR), with a five-method interface where refreshTags and updateTags handle cross-container invalidation. Watch for gotchas: unhandled Redis errors, ReadableStream entries that are single-use, and cache entries that intentionally don't survive deploys. [Read more](https://daily.dev/posts/zqIzQ5JoO) ## Vibe-coded landing pages are turning into a trust signal in reverse There's now a recognizable template for AI-generated startup pages: instrument serif headlines, gratuitous italics, curl-into-bash install scripts, and a 'trusted by' logo row pulled from the same YC batch. Mitchell Hashimoto said he now bounces off products the moment he spots the aesthetic, before ever judging the actual product. Koen Bok's line is the one sticking around: if your site looks vibe coded, people will assume your app is too — the design has become a proxy for how much care went into everything else. [Read more](https://daily.dev/posts/LdzDj5Ylc) ## Same URL, six different pages: how crawlers and LLMs actually see your site An experiment fetched the same MDN page through raw HTTP, Playwright, Googlebot's renderer, Common Crawl, Wayback Machine, and three LLMs with tool use, and got meaningfully different content every time. Playwright's DOM lost 37 code samples trapped in shadow DOM, Common Crawl served a stale build despite being captured after the latest edit, and gemini-3.6-flash silently returned a third of the page while claiming it was complete. If your pipeline does RAG or scraping, this is a good reminder to match the observation layer to the task and verify LLM output against a real fetch instead of trusting a confident-sounding answer. [Read more](https://daily.dev/posts/ms4dv96Mt) --- ## Also notable - **:has() lets you style parents based on child state without touching the DOM:** When you can't safely edit third-party component internals (MUI, Ant Design, AG Grid), the CSS :has() pseudo-class lets you select parent or preceding-sibling elements based on descendant state, something CSS couldn't do before. [Read more](https://daily.dev/posts/7YalpjtNd) - **Custom hooks returning multiple booleans invite invalid states:** A piece on React hook design argues that hooks returning isLoading/isSaving/isSaved/isError independently let TypeScript accept nonsensical combinations, and recommends modeling state as a discriminated union instead, checked against three questions: can values be true together, do they share a lifecycle, and can one be derived from another. [Read more](https://daily.dev/posts/RFuAV7gUX) - **Native Federation in Angular 22 skips the bundler entirely:** A full walkthrough of @angular-architects/native-federation shows it using browser-native ES modules and import maps instead of Webpack Module Federation, covering federation.config.mjs setup, dynamic host manifests, SSR/hydration, and the common NG0919 version-mismatch error. [Read more](https://daily.dev/posts/zbdjJs4yl) ## Similar posts on daily.dev - [Next.js 16.3: Instant Navigations](https://daily.dev/posts/next-js-16-3-instant-navigations-80ncbhrrp) · Next.js · 138 upvotes · 16 comments - [Next.js 16.3: Instant Navigations, Up to 90% Less Dev Memory and Faster Builds](https://daily.dev/posts/next-js-16-3-instant-navigations-up-to-90-less-dev-memory-and-faster-builds-abksajvqx) · InfoQ · 3 upvotes · 1 comments - [How Next.js Got Its Snappy Client Navs Back](https://daily.dev/posts/how-next-js-got-its-snappy-client-navs-back-unrgnqouf) · The New Stack · 0 upvotes · 0 comments --- Tags: [#react](https://daily.dev/tags/react), [#nextjs](https://daily.dev/tags/nextjs), [#redis](https://daily.dev/tags/redis), [#vibe-coding](https://daily.dev/tags/vibe-coding) [View this post on daily.dev](https://daily.dev/posts/next-js-16-3-rewrites-prefetching-vibe-coded-landing-pages-become-a-red-flag-hurvwwupw) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"DiscussionForumPosting","mainEntityOfPage":"https://daily.dev/posts/next-js-16-3-rewrites-prefetching-vibe-coded-landing-pages-become-a-red-flag-hurvwwupw","headline":"Next.js 16.3 rewrites prefetching, vibe-coded landing pages become a red flag","text":"Next.js 16.3 ships Instant Navigations and Partial Prefetching, changing how caching works for anyone on the App Router. A self-hosted Next.js 16 writeup separately tackles the Redis cache-handler problem for multi-container 'use cache' deployments. Developers are publicly turning on the AI-generated landing page aesthetic, with Mitchell Hashimoto and Koen Bok leading the pile-on. A deep dive on scraping the same URL through six different layers shows LLMs and crawlers see very different versions of your pages.","url":"https://daily.dev/posts/next-js-16-3-rewrites-prefetching-vibe-coded-landing-pages-become-a-red-flag-hurvwwupw","datePublished":"2026-08-17T04:19:20.148Z","dateModified":"2026-08-17T04:19:40.504Z","author":{"@type":"Organization","name":"Web Digest","logo":"https://media.daily.dev/image/upload/s--C833eNQW--/f_auto,q_auto/v1773839396/logos/webdev_digest?_a=BAMAMiiu0","url":"https://daily.dev/sources/webdev_digest"},"interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"isPartOf":{"@type":"WebPage","url":"https://daily.dev/sources/webdev_digest","name":"Web Digest"}} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Web Digest","item":"https://daily.dev/sources/webdev_digest"},{"@type":"ListItem","position":3,"name":"Next.js 16.3 rewrites prefetching, vibe-coded landing pages become a red flag"}]} ```