[next] read regions from middleware-manifest output

this PR depends on vercel/next.js#40881
vercel · Sep 25, 2022 · a4892a0 · a4892a0
1 parent 6c9164f
commit a4892a0
Showing 1 changed file with 6 additions and 0 deletions.
diff --git a/packages/next/src/utils.ts b/packages/next/src/utils.ts
@@ -2202,6 +2202,7 @@ interface BaseEdgeFunctionInfo {
   page: string;
   wasm?: { filePath: string; name: string }[];
   assets?: { filePath: string; name: string }[];
+  userConfig?: Record<string, unknown>;
 }
 
 interface EdgeFunctionInfoV1 extends BaseEdgeFunctionInfo {
@@ -2341,6 +2342,11 @@ export async function getMiddlewareBundle({
                   ...wasmFiles,
                   ...assetFiles,
                 },
+                regions:
+                  typeof edgeFunction.userConfig === 'object' &&
+                  'regions' in edgeFunction.userConfig
+                    ? (edgeFunction.userConfig.regions as any)
+                    : 'auto',
                 entrypoint: 'index.js',
                 envVarsInUse: edgeFunction.env,
                 assets: (edgeFunction.assets ?? []).map(({ name }) => {