Install AsyncLocalStorage for appDir rendering (vercel/turborepo#3374)

#44668 refactored Next's use of `AsyncLocalStorage`, and installs a "polyfill" of the API by patching the node import onto `globalThis.` Importantly, it's then used in the module scope during imports, so we need to install the polyfill early in the app rendering startup.

Fixes vercel/turborepo#3319

crates/next-core/js/src/entry/app-renderer.tsx

@@ -29,6 +29,7 @@ import type { RenderData } from "types/turbopack";
 
 import "next/dist/server/node-polyfill-fetch";
 import "next/dist/server/node-polyfill-web-streams";
+import "@vercel/turbopack-next/polyfill/async-local-storage";
 import { RenderOpts, renderToHTMLOrFlight } from "next/dist/server/app-render";
 import { PassThrough } from "stream";
 import { ServerResponseShim } from "@vercel/turbopack-next/internal/http";

crates/next-core/js/src/polyfill/async-local-storage.js

@@ -0,0 +1,6 @@
+// Next.js now creates an AsyncLocalStorage in the module scope, meaning we
+// need to:
+// 1. Install it (it's accessed as `globalthis.AsyncLocalStorage`)
+// 2. Do it in an import (import ordering is guaranteed)
+import { AsyncLocalStorage } from "node:async_hooks";
+globalThis.AsyncLocalStorage = AsyncLocalStorage;

crates/next-core/js/types/globals.d.ts

@@ -20,6 +20,15 @@ declare global {
     page: string,
     paths: string[]
   ): unknown;
+
+  var AsyncLocalStorage = class AsyncLocalStorage<T> {
+    getStore(): T | undefined;
+    run<R, TArgs extends any[]>(
+      store: T,
+      callback: (...args: TArgs) => R,
+      ...args: TArgs
+    ): R;
+  };
 }
 
 export {};