fix: rest api with Next.js basePath option (#10535)

Fixes #10534
payloadcms · Jan 13, 2025 · 04a8083 · 04a8083
1 parent ab564d3
commit 04a8083
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 1 deletion.
diff --git a/packages/next/src/routes/rest/index.ts b/packages/next/src/routes/rest/index.ts
@@ -26,6 +26,7 @@ const handlerBuilder =
     initedOGEndpoint = true
 
     const response = await handleEndpoints({
+      basePath: process.env.NEXT_BASE_PATH,
       config,
       request,
     })

diff --git a/packages/payload/src/utilities/handleEndpoints.ts b/packages/payload/src/utilities/handleEndpoints.ts
@@ -58,9 +58,11 @@ const notFoundResponse = (req: PayloadRequest) => {
  * ```
  */
 export const handleEndpoints = async ({
+  basePath = '',
   config: incomingConfig,
   request,
 }: {
+  basePath?: string
   config: Promise<SanitizedConfig> | SanitizedConfig
   request: Request
 }): Promise<Response> => {
@@ -112,7 +114,7 @@ export const handleEndpoints = async ({
     const { payload } = req
     const { config } = payload
 
-    const pathname = new URL(req.url).pathname
+    const pathname = `${basePath}${new URL(req.url).pathname}`
 
     if (!pathname.startsWith(config.routes.api)) {
       return notFoundResponse(req)