fix: use named wildcards in middleware route in nest v11 (#210)

Closes #205

Author: B4nan

src/middleware.helper.ts

@@ -1,15 +1,23 @@
 import type { MikroOrmMiddlewareModuleOptions, NestMiddlewareConsumer } from './typings';
-import type { MiddlewareConsumer } from '@nestjs/common';
+import { type MiddlewareConsumer, HttpStatus } from '@nestjs/common';
 
 export function forRoutesPath(options: MikroOrmMiddlewareModuleOptions, consumer: MiddlewareConsumer) {
-  const isNestMiddleware = (consumer: MiddlewareConsumer): consumer is NestMiddlewareConsumer => {
-    return typeof (consumer as any).httpAdapter === 'object';
-  };
+  if (options.forRoutesPath) {
+    return options.forRoutesPath;
+  }
+
+  // detect nest v11 based on a newly added enum value
+  if (HttpStatus.MULTI_STATUS) {
+    return '{*all}';
+  }
+
+  const isFastify = (consumer: MiddlewareConsumer) => {
+    if (typeof (consumer as any).httpAdapter !== 'object') {
+      return false;
+    }
 
-  const usingFastify = (consumer: NestMiddlewareConsumer) => {
-    return consumer.httpAdapter.constructor.name.toLowerCase().startsWith('fastify');
+    return (consumer as NestMiddlewareConsumer).httpAdapter.constructor.name.toLowerCase().startsWith('fastify');
   };
 
-  return options.forRoutesPath ??
-    (isNestMiddleware(consumer) && usingFastify(consumer) ? '(.*)' : '*');
+  return isFastify(consumer) ? '(.*)' : '*';
 }