fix(adapter-nextjs): make createAuthRouteHandlers interface work in b…

…oth App and Pages routers

packages/adapter-nextjs/src/auth/createAuthRouteHandlersFactory.ts

@@ -11,9 +11,9 @@ import { AmplifyServerContextError } from '@aws-amplify/core/internals/adapter-c
 
 import {
 	AuthRoutesHandlerContext,
-	CreateAuthRouteHandlers,
 	CreateAuthRouteHandlersFactoryInput,
 	CreateAuthRoutesHandlersInput,
+	InternalCreateAuthRouteHandlers,
 } from './types';
 import {
 	isAuthRoutesHandlersContext,
@@ -28,7 +28,7 @@ export const createAuthRouteHandlersFactory = ({
 	config: resourcesConfig,
 	runtimeOptions = {},
 	runWithAmplifyServerContext,
-}: CreateAuthRouteHandlersFactoryInput): CreateAuthRouteHandlers => {
+}: CreateAuthRouteHandlersFactoryInput): InternalCreateAuthRouteHandlers => {
 	const origin = process.env.AMPLIFY_APP_ORIGIN;
 	if (!origin)
 		throw new AmplifyServerContextError({

packages/adapter-nextjs/src/auth/types.ts

@@ -66,10 +66,20 @@ export interface CreateAuthRoutesHandlersInput {
 	redirectOnSignOutComplete?: string;
 }
 
-export type CreateAuthRouteHandlers = (
+export type InternalCreateAuthRouteHandlers = (
 	input?: CreateAuthRoutesHandlersInput,
 ) => AuthRouteHandlers;
 
+export type CreateAuthRouteHandlers = (
+	input?: CreateAuthRoutesHandlersInput,
+) =>
+	| AuthRouteHandlers
+	// Forcing the handler interface to be any to ensure the single handler can
+	// work in both App Router `routes.ts` and Pages router. The former has a
+	// restrict handler function interface type check. The parameters types are
+	// properly typed internally, and runtime validation is place.
+	| any;
+
 export interface CreateAuthRouteHandlersFactoryInput {
 	config: ResourcesConfig;
 	runtimeOptions: NextServer.CreateServerRunnerRuntimeOptions | undefined;