Skip to content

fix: under Next.js always fetch so every route revalidates (0.2.4) - #7

Merged
ralyodio merged 1 commit into
mainfrom
fix/next-every-route-revalidates
Oct 10, 2026
Merged

ralyodio merged 1 commit into
mainfrom
fix/next-every-route-revalidates

Conversation

@ralyodio

Copy link
Copy Markdown
Contributor

Pages rendered after the first at next build got the template from the in-memory cache, so Next saw no revalidating fetch on them and made them fully static (s-maxage=31536000); coinpayportal's homepage never picked up 0.2.2. Under Next (detected by fetch.__nextPatched, verified in next 16.3.8, or NEXT_RUNTIME) every render goes through fetch with next.revalidate = 300. Test added.

🤖 Generated with Claude Code

At build time the first page fetched the template and every later page got it
from the in-memory cache, so Next never saw a revalidating fetch on those
routes and served them with s-maxage=31536000: coinpayportal's homepage never
picked up 0.2.2. Under Next (patched fetch or NEXT_RUNTIME) go through fetch on
every render and let Next's data cache (revalidate 300 s) do the caching.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ralyodio
ralyodio merged commit 0d6fe5a into main Oct 10, 2026
3 checks passed
@ralyodio
ralyodio deleted the fix/next-every-route-revalidates branch October 10, 2026 19:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant