securenow 6.0.0 → 6.0.2

package/docs/CHANGELOG-NEXTJS.md

@@ -1,5 +1,39 @@
 # Changelog - Next.js Support
 
+## Version 6.0.1 (Logging hotfix)
+
+### 🐛 Bug Fixes
+
+- **Fixed: `logger.emit()` silently dropped every log record in 6.0.0.**
+  `tracing.js` constructed the `LoggerProvider` with `{ processors: [new
+  BatchLogRecordProcessor(...)] }`, but that constructor option was only added
+  in `@opentelemetry/sdk-logs` 0.52 — the pinned 0.47.x silently ignores it,
+  leaving the provider with a `NoopLogRecordProcessor`. Every `logger.emit()`
+  (and every auto-captured `console.*`) was dropped, and `forceFlush()`
+  resolved with nothing to export. No HTTP POST ever reached `/v1/logs`.
+  Traces were unaffected (separate pipeline). Fixed by calling
+  `loggerProvider.addLogRecordProcessor(...)` after construction, matching the
+  0.47.x API.
+
+### ✨ Improvements
+
+- **`registerSecureNow()` (Next.js) now wires the OTLP logs pipeline.** In
+  6.0.0, `securenow/nextjs` only set up traces — calling `registerSecureNow()`
+  with `SECURENOW_LOGGING_ENABLED=1` would log the "ENABLED" banner but emit
+  nothing. 6.0.1 creates a `LoggerProvider`, registers a
+  `BatchLogRecordProcessor(OTLPLogExporter)`, publishes it via
+  `logs.setGlobalLoggerProvider()`, and auto-patches
+  `console.log/info/warn/error/debug` to emit OTLP log records. Works on both
+  the Vercel (`@vercel/otel`) and self-hosted (`NodeSDK`) code paths. Graceful
+  flush + shutdown registered on SIGINT/SIGTERM/beforeExit.
+- **`tracing.js` now calls `logs.setGlobalLoggerProvider()`** so consumers can
+  retrieve the logger via `@opentelemetry/api-logs` without depending on the
+  module export.
+- **Docs updated** (`NPM_README.md`, `docs/LOGGING-QUICKSTART.md`) to
+  recommend `registerSecureNow` from `securenow/nextjs` for Next.js apps
+  instead of `securenow/register` + `securenow/console-instrumentation`
+  (which boots a full `NodeSDK` and conflicts with Next.js / `@vercel/otel`).
+
 ## Version 3.1.0 (Next.js Support Added)
 
 ### 🎉 New Features

package/docs/LOGGING-QUICKSTART.md

@@ -101,13 +101,21 @@ app.listen(3000);
 
 ### Next.js
 
+Next.js apps must use `securenow/nextjs` (not `securenow/register`, which
+boots a full NodeSDK and conflicts with Next.js / `@vercel/otel`). Since
+**6.0.1**, `registerSecureNow()` sets up the OTLP logs pipeline and auto-
+patches `console.*` whenever `SECURENOW_LOGGING_ENABLED=1` is set — on both
+Vercel and self-hosted (EC2, PM2, Docker) environments.
+
 ```typescript
 // instrumentation.ts (in project root)
 export async function register() {
   if (process.env.NEXT_RUNTIME === 'nodejs') {
+    // Must be set BEFORE loading securenow/nextjs
     process.env.SECURENOW_LOGGING_ENABLED = '1';
-    await import('securenow/register');
-    await import('securenow/console-instrumentation');
+
+    const { registerSecureNow } = await import('securenow/nextjs');
+    registerSecureNow({ captureBody: true });
   }
 }
 ```
@@ -119,6 +127,14 @@ SECURENOW_APPID=my-nextjs-app
 SECURENOW_INSTANCE=http://localhost:4318
 ```
 
+Enable the instrumentation hook in `next.config.js`:
+
+```javascript
+module.exports = {
+  experimental: { instrumentationHook: true },
+};
+```
+
 ### Fastify
 
 ```javascript