yinzerflow 0.6.12 → 0.7.0

package/CHANGELOG.md

@@ -1,5 +1,39 @@
 # Changelog
 
+## [0.7.0] - 2026-02-20
+
+### Bug Fixes
+
+- **Clarify log level threshold behavior** — Fixed logging logic to properly enforce log level thresholds, ensuring messages below the configured level are correctly filtered (f2ff105)
+
+### Internal
+
+- **Move bundle check to preflight in publish workflow** — Reorganized publish process to validate bundles earlier in the pipeline (4b42643)
+- **Improve type safety across core flow** — Enhanced type annotations and removed unsafe `typeof` checks in favor of explicit interfaces (36eb059, 1f29acf, 266a1bd)
+- **Restructure logging into three independent channels** — Refactored logging system to separate concerns with per-instance loggers instead of a global singleton, improving isolation and testability (bb7d752, dc9738d, 534c8e7, 86e1207, 5b769d3, 8c10c1f)
+- **Inject logger dependencies throughout middleware** — Threaded logger instances through cookie parser, rate limiter, and hook registry instead of relying on global state (874f6a4, e8277b3)
+- **Consolidate logging configuration** — Unified logging config handling and clarified log level documentation in InternalConfiguration (15b9158, e9888db)
+- **Improve utility functions** — Enhanced time utilities validation logic, added byte size conversion helpers, and removed unused utility functions (2e2a0bf, 004df51, 5e70bd2)
+- **Verify npm credentials before git operations** — Updated publish script to check npm access before attempting git pushes (65dbead)
+- **Remove dayjs dependency** — Eliminated unnecessary dayjs library from project dependencies (36c57ba)
+
+## [0.6.14] - 2026-02-20
+
+### Bug Fixes
+
+- **Use correct API key environment variable** — Fixed publish script to reference the proper API key environment variable for changelog generation (c4f420c)
+
+### Internal
+
+- **Enhance preflight checks in publish script** — Refactored preflight validation logic to improve robustness of the publish process (09ad711)
+- **Require API key for changelog generation** — Updated publish configuration to enforce API key presence when generating changelogs (04bfd70)
+
+## [0.6.13] - 2026-02-20
+
+- ``` 🔧 chore: update progress to Phase 2 (7a55239)
+- ♻️ refactor(hook-registry): fix typo in error log (057a458)
+- ♻️ refactor(request-response-handling): optimize headers (a133d7c)
+
 All notable changes to YinzerFlow will be documented in this file.
 
 ## [0.6.12] - 2026-02-20

package/docs/configuration/configuration.md

@@ -69,81 +69,44 @@ Options: `string`
 
 </aside>
 
-### logger — @default <span style="color: #2ecc71">`undefined`</span>
+### logging — @default <span style="color: #2ecc71">`{ level: 'warn', prefix: 'YINZER', personality: true, requests: false }`</span>
 
-Custom logger instance for application logs.
-
-<span style="color: #3498db">**💡 Tip:**</span> Use `createLogger()` to create custom logger instances with different prefixes or log levels.
+Logging configuration — controls app logger, access logs, and diagnostics. Three independent channels under one key.
 
 ```typescript
-import { YinzerFlow, createLogger } from "yinzerflow";
-
-const customLogger = createLogger({ 
-  prefix: "MY-APP", 
-  logLevel: "info" 
-});
-
-const app = new YinzerFlow({
-  port: 3000,
-  logger: customLogger,
-});
-```
-
-<aside>
-
-Options: `Logger | undefined`
-
-- ✅ `undefined`: Uses built-in logger (default)
-- 🎨 `Logger`: Custom logger instance via `createLogger()`
-
-<span style="color: #3498db">🔗 See [Logging Documentation](../core/logging.md) for details</span>
-
-</aside>
-
-### networkLogs — @default <span style="color: #2ecc71">`false`</span>
-
-Enable nginx-style network request/response logging.
-
-<span style="color: #e74c3c">**⚠️ Warning:**</span> Network logs are separate from application logs and can generate significant output in high-traffic scenarios.
+import { YinzerFlow } from "yinzerflow";
 
-```typescript
 const app = new YinzerFlow({
   port: 3000,
-  networkLogs: true, // Enable network logging
+  logging: {
+    level: "info",             // 'off' | 'error' | 'warn' | 'info' | 'debug'
+    prefix: "MY-APP",         // Log line prefix: [MY-APP]
+    personality: true,         // Pittsburgh personality phrases
+    requests: true,            // nginx-style access logs
+    logger: winstonLogger,     // Custom app logger (optional)
+    accessLogger: pinoLogger,  // Custom access logger (optional)
+    diagnostics: {             // Framework health monitoring
+      slowRequests: "500ms",
+      largeResponses: "1mb",
+      memory: "30s",
+      eventLoop: "100ms",
+      rateLimits: true,
+    },
+  },
 });
 ```
 
 <aside>
 
-Options: `boolean`
-
-- 🔴 `false`: Disabled (default, recommended for production)
-- 🟢 `true`: Enabled (useful for debugging)
-
-</aside>
-
-### networkLogger — @default <span style="color: #2ecc71">`undefined`</span>
-
-Custom logger for network logs (nginx-style request/response logging).
+Key settings:
 
-```typescript
-import { YinzerFlow, createLogger } from "yinzerflow";
+- 🔊 `level`: Minimum app log level (`'warn'` default)
+- 🏷️ `prefix`: Log line prefix (`'YINZER'` default)
+- 🎭 `personality`: Pittsburgh phrases (`true` default)
+- 📊 `requests`: Access logs on/off (`false` default)
+- 🔧 `diagnostics`: Health monitoring thresholds (all `false` default)
 
-const networkLogger = createLogger({ prefix: "NETWORK" });
-
-const app = new YinzerFlow({
-  port: 3000,
-  networkLogs: true,
-  networkLogger, // Route network logs to custom logger
-});
-```
-
-<aside>
-
-Options: `Logger | undefined`
-
-- ✅ `undefined`: Uses built-in network logging format (default)
-- 🎨 `Logger`: Custom logger for network logs
+<span style="color: #3498db">🔗 See [Logging Documentation](../core/logging.md) for all options, diagnostic presets, and `createLogger()` usage</span>
 
 </aside>
 
@@ -293,7 +256,7 @@ Options: `TimeString | number`
 
 - ✅ **Use environment variables**: Store configuration in environment variables for different environments
 - 🔒 **Start secure**: Begin with strict limits and relax as needed
-- 📊 **Enable logging**: Use `networkLogs: true` in development for debugging
+- 📊 **Enable logging**: Use `logging: { requests: true }` in development for debugging
 - 🎯 **Validate configuration**: Test configuration before deploying to production
 - 🔑 **Configure proxies**: Set `trustedProxies` for load balancers and CDNs
 - ⚡ **Optimize for use case**: Adjust limits based on your specific workload
@@ -364,7 +327,10 @@ import { YinzerFlow } from "yinzerflow";
 
 const app = new YinzerFlow({
   port: 3000,
-  networkLogs: true, // Verbose request logging
+  logging: {
+    level: "debug",
+    requests: true, // Verbose request logging
+  },
   cors: {
     enabled: true,
     origin: "*", // Allow all origins (DEV ONLY!)
@@ -588,7 +554,10 @@ const app = new YinzerFlow({
   port: parseInt(process.env.PORT || "3000"),
   host: process.env.HOST || "0.0.0.0",
   
-  networkLogs: isDevelopment, // Only in development
+  logging: {
+    level: isDevelopment ? "debug" : "warn",
+    requests: isDevelopment, // Only in development
+  },
   
   cors: {
     enabled: true,