🤖 Merge PR DefinitelyTyped#49933 [pino-http] fix: Declare support for…

… the optional `next` parameter by @kf6kjg

The actual code handles it just fine, it looks like it was a simple omission.

With this in place, as my locally patched edition has it, I can use AsyncLocalStorage to keep the logger context across the whole request.

types/pino-http/index.d.ts

@@ -16,7 +16,7 @@ declare function PinoHttp(opts?: PinoHttp.Options, stream?: DestinationStream):
 declare function PinoHttp(stream?: DestinationStream): PinoHttp.HttpLogger;
 
 declare namespace PinoHttp {
-    type HttpLogger = (req: IncomingMessage, res: ServerResponse) => void;
+    type HttpLogger = (req: IncomingMessage, res: ServerResponse, next?: () => void) => void;
     type ReqId = number | string | object;
 
     /**

types/pino-http/pino-http-tests.ts

@@ -13,6 +13,13 @@ function handle(req: http.IncomingMessage, res: http.ServerResponse) {
     res[pinoHttp.startTime] = Date.now();
 }
 
+function handle_with_next(req: http.IncomingMessage, res: http.ServerResponse, next: () => void) {
+    pinoHttp()(req, res, () => {
+        // Do a thing.
+        next();
+    });
+}
+
 pinoHttp({ logger });
 pinoHttp({ genReqId: req => req.statusCode || 200 });
 pinoHttp({ genReqId: req => 'foo' });