Shu Ding b7d438cfc1 Invalidate prefetch cache when a tag or path has been revalidated on the server (#50848) ... This makes sure that if `revalidateTag` is called in a Server Action, the client router cache and prefetch cache are invalidated correctly so following navigations won't reuse the cache that might hold stale data. Similar case for `revalidatePath`. I left a TODO where we can't just invalidate the subtree under the revalidate paths because of current implementation limitations. To ensure correctness, we just do the same as `revalidateTag`.		2023-06-08 13:44:42 +00:00
..
app	Invalidate prefetch cache when a tag or path has been revalidated on the server (#50848)	2023-06-08 13:44:42 +00:00
app-action-export.test.ts	Fix missing error when using Actions on the client layer without enabling the feature flag (#50257)	2023-05-25 14:22:27 +02:00
app-action-invalid.test.ts	Fix missing error when using Actions on the client layer without enabling the feature flag (#50257)	2023-05-25 14:22:27 +02:00
app-action.test.ts	Invalidate prefetch cache when a tag or path has been revalidated on the server (#50848)	2023-06-08 13:44:42 +00:00
next.config.js	Add test case for client sourcemaps (#49308)	2023-05-05 14:23:04 +00:00