Middleware class

README.md

@@ -31,7 +31,7 @@ A lightweight library that brings some structure to Express.js
 
 Check the `/example` folder for a basic todo app with database integration.
 
-Sapling is also powering one of my more complex projects with 400+ users in production, which you can view at [instalock-web](https://github.com/tahminator/instalock-web).
+Sapling is also powering one of my more complex projects with 600+ users in production, which you can view at [instalock-web](https://github.com/tahminator/instalock-web).
 
 ## Install
 
@@ -188,7 +188,7 @@ import { Controller, Middleware } from "@tahminator/sapling";
 import cookieParser from "cookie-parser";
 import { NextFunction, Request, Response } from "express";
 
-@Controller()
+@MiddlewareClass() // works the same as @Controller, semantically different
 class CookieParserMiddleware {
   private readonly plugin: ReturnType<typeof cookieParser>;
 

package.json

@@ -12,7 +12,8 @@
   "exports": {
     ".": {
       "types": "./dist/index.d.ts",
-      "import": "./dist/index.js"
+      "import": "./dist/index.js",
+      "require": "./dist/index.js"
     }
   },
   "files": [

src/annotation/index.ts

@@ -1,3 +1,4 @@
 export * from "./controller";
 export * from "./injectable";
 export * from "./route";
+export * from "./middleware";

src/annotation/middleware.ts

@@ -0,0 +1,14 @@
+import { Controller } from "./controller";
+
+/**
+ * Used to define a middleware-only class.
+ *
+ * __NOTE:__ `@MiddlewareClass` works exactly the same as `@Controller`. As such, you
+ * can still register `@Route` and `@Middleware` methods, though you very well should not
+ * for the sake of semantics.
+ */
+export function MiddlewareClass(
+  ...args: Parameters<typeof Controller>
+): ClassDecorator {
+  return Controller(...args);
+}