chore: fix type issues

Author: pi0

src/presets/_nitro/runtime/nitro-dev.ts

@@ -10,6 +10,7 @@ import { startScheduleRunner } from "#nitro/runtime/task";
 import { trapUnhandledErrors } from "#nitro/runtime/error/hooks";
 import { resolveWebsocketHooks } from "#nitro/runtime/app";
 import { hasWebSocket } from "#nitro/virtual/feature-flags";
+import type { NodeHttp1Handler } from "srvx";
 
 // Listen for shutdown signal from runner
 parentPort?.on("message", (msg) => {
@@ -23,7 +24,7 @@ const nitroHooks = useNitroHooks();
 
 trapUnhandledErrors();
 
-const server = new Server(toNodeHandler(nitroApp.fetch));
+const server = new Server(toNodeHandler(nitroApp.fetch) as NodeHttp1Handler);
 let listener: Server | undefined;
 
 listen()

src/presets/aws-amplify/runtime/aws-amplify.ts

@@ -2,11 +2,12 @@ import "#nitro/virtual/polyfills";
 import { useNitroApp } from "nitro/app";
 
 import { Server } from "node:http";
+import type { NodeHttp1Handler } from "srvx";
 import { toNodeHandler } from "srvx/node";
 
 const nitroApp = useNitroApp();
 
-const server = new Server(toNodeHandler(nitroApp.fetch));
+const server = new Server(toNodeHandler(nitroApp.fetch) as NodeHttp1Handler);
 
 // @ts-ignore
 server.listen(3000, (err) => {

src/presets/vercel/runtime/vercel.node.ts

@@ -24,5 +24,5 @@ export default function nodeHandler(
     }
   }
 
-  return handler(req, res);
+  return handler(req as any, res as any);
 }