Next.js ISR Revalidation Stuck Serving Stale Pages
An ISR page keeps serving cached HTML for hours past its revalidate window — almost always a CDN cache shadowing, build-output drift, or on-demand path mismatch.
Articles tagged with #Next.js
An ISR page keeps serving cached HTML for hours past its revalidate window — almost always a CDN cache shadowing, build-output drift, or on-demand path mismatch.
Contentlayer was great until it stopped being maintained. Here is how the MDX-bundler / next-mdx-remote path compares in 2026 — DX, build time, type safety, and lock-in.
Editors should not wait for a redeploy to see a typo fix. Here is how to wire on-demand revalidation in App Router — webhook, secret, path vs tag, and how to test it works.
Next.js App Router code review prompts — server vs client boundaries, server actions, route handlers, fetch caching, revalidation, streaming.
A side-by-side comparison of Astro and Next.js for content sites in 2026, with concrete decision criteria and the real long-term cost of each.
You do not need a 20-hour tutorial on App Router. You need the eight concepts that explain why your code does what it does. Here they are.
Next.js does not break SEO, but it has footguns. Use this metadata API, sitemap.ts, and view-source checklist before you ask Google to crawl.
Step-by-step 2026 guide to deploying Next.js on Vercel — auto-detection, environment variables, ISR, image optimization, and the App Router gotchas indie devs lose half a day to.
`next/image` is the single biggest performance win you get for free — if you actually configure it. Here are the four things to set right.
A correctly served sitemap and robots.txt are non-negotiable for SEO. Here is the App Router idiom for both in 2026.
Next.js is the default React framework in 2026 — but defaulting to it for a content site can cost you speed, hosting bills, and weekends. Here is when it is the right call.
Static and SSR look interchangeable on a Next.js project until you scale, ship, or pay the bill. Here is how to pick correctly for a content site in 2026.
Spot the Next.js-for-content mismatch with build-time + bundle-size benchmarks, Lighthouse diff, and a phased Astro migration plan.