temp-fix: rendering error in next.js 14.0.2 caused by next.js bug (#534)

cloudflare · Nov 11, 2023 · c83d125 · c83d125
1 parent bf57ec9
commit c83d125
Show file tree

Hide file tree

Showing 2 changed files with 13 additions and 0 deletions.
diff --git a/.changeset/eighty-spoons-decide.md b/.changeset/eighty-spoons-decide.md
@@ -0,0 +1,5 @@
+---
+'@cloudflare/next-on-pages': patch
+---
+
+Temporary hotfix for `vercel/next.js#58265` so that rendering in Next.js >= 14.0.2 works.
diff --git a/packages/next-on-pages/src/buildApplication/processVercelFunctions/dedupeEdgeFunctions.ts b/packages/next-on-pages/src/buildApplication/processVercelFunctions/dedupeEdgeFunctions.ts
@@ -484,6 +484,14 @@ function fixFunctionContents(contents: string): string {
 		'$1',
 	);
 
+	// TODO: Remove once https://github.com/vercel/next.js/issues/58265 is fixed.
+	// This resolves a critical issue in Next.js 14.0.2 that breaks edge runtime rendering due to the assumption
+	// that the the passed internal request is of type `NodeNextRequest` and never `WebNextRequest`.
+	contents = contents.replace(
+		/;let{originalRequest:(\w+)}=(\w+);/gm,
+		';let{originalRequest:$1=$2}=$2;',
+	);
+
 	return contents;
 }