fixup! enable getCloudflareContext to work in middlewares via a new…

… `enableEdgeDevGetCloudflareContext` utility

create new `monkeyPatchVmModuleEdgeContext` commented function

packages/cloudflare/src/api/cloudflare-context.ts

@@ -112,6 +112,19 @@ type RuntimeContext = Record<string, unknown> & {
  * Note: this function should only be called inside the Next.js config file
  */
 export async function enableEdgeDevGetCloudflareContext() {
+  await monkeyPatchVmModuleEdgeContext();
+}
+
+/**
+ * Next.js uses the Node.js vm module's `runInContext()` function to evaluate the edge functions
+ * in a runtime context that tries to simulate as accurately as possible the actual production runtime
+ * behavior, see: https://github.com/vercel/next.js/blob/9a1cd3/packages/next/src/server/web/sandbox/context.ts#L525-L527
+ *
+ * This function monkey-patches the Node.js `vm` module to override the `runInContext()` function so that the
+ * cloudflare context (which is created using the platform proxy obtained via wrangler's `getPlatformProxy` utility)
+ * can be added to the runtime context's `process.env` before the actual edge functions are evaluated.
+ */
+async function monkeyPatchVmModuleEdgeContext() {
   const require = (
     await import(/* webpackIgnore: true */ `${"__module".replaceAll("_", "")}`)
   ).default.createRequire(import.meta.url);