diff --git a/.changeset/rework-logger-transports.md b/.changeset/rework-logger-transports.md deleted file mode 100644 index 65db60b0..00000000 --- a/.changeset/rework-logger-transports.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@wolfstar/plugin-logger": minor ---- - -feat(plugin-logger)!: derive a shared `message`, `error` and `context` on every payload, and rework the Sentry, evlog and winston transports on top of them. `LogPayload` gains the three fields (see `createLogPayload`, for custom transports and tests). `SentryTransport` keeps the message and context next to an exception, can record breadcrumbs (`breadcrumbLevel`) and send Sentry Logs (`logLevel`), and flushes the client on close; the `@sentry/node` peer dependency is dropped. `EvlogTransport` now writes structured events through evlog's pipeline instead of flattened strings, maps all six levels, and flushes the `drain` on close; the `evlog` peer is raised to `^2.30.0`. `WinstonTransport` serialises errors, flags `fatal` entries, and no longer hangs when closed twice. The Stars module gains an `evlog` option that runs `initLogger` and adds the transport: `evlog: true`, or the options written inline (`env`, `sampling`, `redact`, `pipeline`, ...) with `drain` pointing to a file default-exporting `defineEvlogDrain(...)` (new `@wolfstar/plugin-logger/evlog/plugin` entry, whose default export is the plugin factory taking the drain directly outside Stars). The evlog plugin also emits one evlog wide event per interaction (command, component, modal, optionally autocomplete) with its outcome, error, duration and who/where, controlled by the `interactions` option, and `useInteractionLogger()` adds fields to it from the code of a command. diff --git a/packages/plugin-logger/CHANGELOG.md b/packages/plugin-logger/CHANGELOG.md index eb0678c9..0a1311eb 100644 --- a/packages/plugin-logger/CHANGELOG.md +++ b/packages/plugin-logger/CHANGELOG.md @@ -1,5 +1,11 @@ # @wolfstar/plugin-logger +## 0.4.0 + +### Minor Changes + +- [#232](https://github.com/wolfstar-project/plugins/pull/232) [`0dc1020`](https://github.com/wolfstar-project/plugins/commit/0dc1020dfa9eb71eb6fc971987437aa3aa7ac14a) - feat(plugin-logger)!: derive a shared `message`, `error` and `context` on every payload, and rework the Sentry, evlog and winston transports on top of them. `LogPayload` gains the three fields (see `createLogPayload`, for custom transports and tests). `SentryTransport` keeps the message and context next to an exception, can record breadcrumbs (`breadcrumbLevel`) and send Sentry Logs (`logLevel`), and flushes the client on close; the `@sentry/node` peer dependency is dropped. `EvlogTransport` now writes structured events through evlog's pipeline instead of flattened strings, maps all six levels, and flushes the `drain` on close; the `evlog` peer is raised to `^2.30.0`. `WinstonTransport` serialises errors, flags `fatal` entries, and no longer hangs when closed twice. The Stars module gains an `evlog` option that runs `initLogger` and adds the transport: `evlog: true`, or the options written inline (`env`, `sampling`, `redact`, `pipeline`, ...) with `drain` pointing to a file default-exporting `defineEvlogDrain(...)` (new `@wolfstar/plugin-logger/evlog/plugin` entry, whose default export is the plugin factory taking the drain directly outside Stars). The evlog plugin also emits one evlog wide event per interaction (command, component, modal, optionally autocomplete) with its outcome, error, duration and who/where, controlled by the `interactions` option, and `useInteractionLogger()` adds fields to it from the code of a command. + ## 0.3.0 ### Minor Changes diff --git a/packages/plugin-logger/package.json b/packages/plugin-logger/package.json index e1bee083..fd443779 100644 --- a/packages/plugin-logger/package.json +++ b/packages/plugin-logger/package.json @@ -1,6 +1,6 @@ { "name": "@wolfstar/plugin-logger", - "version": "0.3.0", + "version": "0.4.0", "description": "Plugin for @wolfstar/http-framework providing a pluggable logger with swappable transports (console, Sentry, consola, evlog, winston)", "keywords": [ "consola",