@autofleet/logger 4.5.0 → 4.5.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@autofleet/logger",
-  "version": "4.5.0",
+  "version": "4.5.2",
   "description": "",
   "type": "module",
   "main": "./dist/index.js",

package/readme.md

@@ -19,15 +19,14 @@ logger.debug('debug with object', { a: 5 });
 
 Use `addToContext` to attach fields that automatically appear on every log within the same async request chain, isolated per concurrent request.
 
-**HTTP (Express / super-express)** — add `loggerContextMiddleware` once at the app level:
+**HTTP with `super-express`** — `loggerContextMiddleware` is registered automatically, just call `addToContext` anywhere in the request lifecycle:
 
 ```js
-import Logger, { loggerContextMiddleware } from '@autofleet/logger';
+import Logger from '@autofleet/logger';
 
 const logger = Logger();
-app.use(loggerContextMiddleware);
 
-// Then anywhere in the request lifecycle:
+// No setup needed — super-express handles it
 logger.addToContext({ requestId: req.id });  // in middleware
 logger.addToContext({ userId });              // after auth
 logger.addToContext({ orderId: order.id });  // in route handler
@@ -35,6 +34,22 @@ logger.addToContext({ orderId: order.id });  // in route handler
 logger.info('order created'); // → { requestId, userId, orderId, message: 'order created', ... }
 ```
 
+**HTTP with plain Express** — register `loggerContextMiddleware` manually at the app level:
+
+```js
+import Logger, { loggerContextMiddleware } from '@autofleet/logger';
+
+const logger = Logger();
+app.use(loggerContextMiddleware);
+
+// Then anywhere in the request lifecycle:
+logger.addToContext({ requestId: req.id });
+logger.addToContext({ userId });
+logger.addToContext({ orderId: order.id });
+
+logger.info('order created'); // → { requestId, userId, orderId, message: 'order created', ... }
+```
+
 **RabbitMQ / Kafka consumers** — wrap the handler with `runWithLoggerContext`:
 
 ```js