fix: clientContext isn't available in background functions (#2121)

Skn0tt · web-flow · commit df0f6bcecee3 · 2023-05-17T09:34:20.000Z
diff --git a/packages/runtime/src/templates/getApiHandler.ts b/packages/runtime/src/templates/getApiHandler.ts
@@ -70,9 +70,7 @@ const makeApiHandler = ({ conf, app, pageRoot, NextServer }: MakeApiHandlerParam
       return bridge
     }
 
-    const {
-      clientContext: { custom: customContext },
-    } = context
+    const customContext = context.clientContext?.custom
 
     // Scheduled functions don't have a URL, but we need to give one so Next knows the route to serve
     const url = event.rawUrl ? new URL(event.rawUrl) : new URL(path, process.env.URL || 'http://n')

Original file line number	Diff line number	Diff line change
`@@ -70,9 +70,7 @@ const makeApiHandler = ({ conf, app, pageRoot, NextServer }: MakeApiHandlerParam`
`70`	`70`	`return bridge`
`71`	`71`	`}`
`72`	`72`
`73`		`- const {`
`74`		`- clientContext: { custom: customContext },`
`75`		`- } = context`
	`73`	`+ const customContext = context.clientContext?.custom`
`76`	`74`
`77`	`75`	`// Scheduled functions don't have a URL, but we need to give one so Next knows the route to serve`
`78`	`76`	`const url = event.rawUrl ? new URL(event.rawUrl) : new URL(path, process.env.URL \|\| 'http://n')`