Fix TypedNextResponse usage

The custom typings do not implement
the same constuctor as the original
NextResponse class, so we apply the
custom types to the original NextResponse
class when exporting the module instead.

packages/next-rest-framework/src/index.ts

@@ -1,8 +1,12 @@
+import { NextResponse } from 'next/server';
+import { type TypedNextResponse as TypedNextResponseType } from './types';
 export {
   routeHandler,
   routeOperation,
   apiRouteHandler,
   apiRouteOperation
 } from './route-handlers';
 export { docsRouteHandler, docsApiRouteHandler } from './docs-handlers';
-export { TypedNextResponse } from './types';
+
+// @ts-expect-error - Keep the original NextResponse functionality with custom types.
+export const TypedNextResponse: typeof TypedNextResponseType = NextResponse;

packages/next-rest-framework/src/types/route-handlers.ts

@@ -159,7 +159,7 @@ export type RouteOperation = (
 export type NextRouteHandler = (
   req: NextRequest,
   context: { params: BaseQuery }
-) => Promise<NextResponse>;
+) => Promise<NextResponse> | NextResponse | Promise<void> | void;
 
 export interface RouteOperationDefinition {
   _config: {