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: .changeset/thirty-dogs-play.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,4 +2,6 @@
2
2
'@vercel/edge-config': patch
3
3
---
4
4
5
-
Suppress errors thrown by cacheLife for contexts where the next-js condition is set but "use cache" functions are not turned into Cache Functions
5
+
Support Next.js v16 Cache Components even within `proxy.ts` (fka `middleware.ts`) - see [#890](https://github.com/vercel/storage/pull/890)
6
+
7
+
The `@vercel/edge-config` v1.4.1 release added support for Next.js v16 `cacheComponents`, but did not support using `@vercel/edge-config` in Next.js's `proxy.ts` (fka `middleware.ts`) when the `cacheComponents` flag was enabled in `next.config.ts`. This releases fixes this issue so `@vercel/edge-config` can be used in any server side context in Next.js again.
0 commit comments