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
Copy file name to clipboardExpand all lines: README.md
+10-7Lines changed: 10 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -414,16 +414,19 @@ This cost estimate is based on the `us-east-1` region pricing and does not consi
414
414
415
415
#### WORKAROUND: Patch fetch behaviour for ISR. Only for [email protected]+
416
416
417
-
In order to make fetch work as expected with ISR, you need to patch the `fetch` function in your app. Just add this lines to your root layout component:
417
+
If you use ISR and fetch in your app, you may encounter a bug that makes your revalidate values inconsistent.
418
+
The issue is that it revalidates using the lowest revalidate of all fetch calls in your page, regardless of their individual values. To fix this bug, you need to modify the fetch function in your root layout component with the following code snippet
Without this workaround, if you have 2 fetch calls in your page with different revalidate values, both will use the smallest value during ISR revalidation.
427
430
428
431
#### WORKAROUND: Create one cache behavior per top-level file and folder in `public/` (AWS specific)
0 commit comments