You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Visualize the Full Route Cache revalidation time (in seconds) per route
Non-Goals
No response
Background
The revalidation time of a route is known.
However, when developing it is quite hard and very time-consuming to exactly know what the revalidation time of a route is. As you have to dig through every request that is happening across each layout and page of a single route.
As stated in the documentation:
"The lowest revalidate across each layout and page of a single route will determine the revalidation frequency of the entire route. This ensures that child pages are revalidated as frequently as their parent layouts."
It would be very pleasing to see the revalidation time in seconds per route on the build output of next build.
This could go in a seperate column Revalidate (s), just like the Size and First Load JS columns.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Goals
Visualize the Full Route Cache revalidation time (in seconds) per route
Non-Goals
No response
Background
The revalidation time of a route is known.
However, when developing it is quite hard and very time-consuming to exactly know what the revalidation time of a route is. As you have to dig through every request that is happening across each layout and page of a single route.
As stated in the documentation:
revalidate
across each layout and page of a single route will determine the revalidation frequency of the entire route. This ensures that child pages are revalidated as frequently as their parent layouts."fetch
requests can set a lowerrevalidate
than the route's defaultrevalidate
to increase the revalidation frequency of the entire route. This allows you to dynamically opt-in to more frequent revalidation for certain routes based on some criteria."https://nextjs.org/docs/app/api-reference/file-conventions/route-segment-config#revalidation-frequency
Proposal
It would be very pleasing to see the revalidation time in seconds per route on the build output of
next build
.This could go in a seperate column
Revalidate (s)
, just like theSize
andFirst Load JS
columns.Beta Was this translation helpful? Give feedback.
All reactions