fix: fix basePath support for API routes

Fixes: #522
opennextjs · Sep 23, 2024 · 7fad04d · 7fad04d
1 parent 388b4e7
commit 7fad04d
Showing 1 changed file with 7 additions and 2 deletions.
diff --git a/packages/open-next/src/core/routingHandler.ts b/packages/open-next/src/core/routingHandler.ts
@@ -34,6 +34,11 @@ const optionalBasepathPrefixRegex = !!RoutesManifest.basePath
   ? `^${RoutesManifest.basePath}/?`
   : "^/";
 
+// Add the basePath prefix to the api routes
+const apiPrefix = !!RoutesManifest.basePath
+  ? `${RoutesManifest.basePath}/api`
+  : "/api";
+
 const staticRegexp = RoutesManifest.routes.static.map(
   (route) =>
     new RegExp(
@@ -145,8 +150,8 @@ export default async function routingHandler(
   // /api even if it's a page route doesn't get generated in the manifest
   // Ideally we would need to properly check api routes here
   const isApiRoute =
-    internalEvent.rawPath === "/api" ||
-    internalEvent.rawPath.startsWith("/api/");
+    internalEvent.rawPath === apiPrefix ||
+    internalEvent.rawPath.startsWith(`${apiPrefix}/`);
 
   const isNextImageRoute = internalEvent.rawPath.startsWith("/_next/image");