@wolfstar/plugin-logger. For the weekly summary across all packages, see the changelog overview.
0.5.0 (2026-10-20)
New features
- Own
stars.configkey — The module setsmeta.configKey, so you can write its options under the top-levelloggerkey ofstars.configinstead of the[specifier, options]tuple ofmodules. The tuple still works and is merged over the key. The key is typed indefineConfigonce the module is imported instars.config.ts. (#259)
Updates
- New optional peer —
@wolfstar/schema(^0.9.0) is a new optional peer that carries theStarsConfigtype the keys extend.
Migration
@wolfstar/kitpeer raised — The@wolfstar/kitpeer range moves from^0.1.0to^0.2.0, the first version that readsconfigKey. If your project uses@wolfstar/kit0.1, update it.
0.4.0 (2026-10-09)
New features
- Shared payload fields — Every
LogPayloadnow carries a derivedmessage,error, andcontext. UsecreateLogPayloadto build payloads for custom transports and tests. (#232) evlogmodule option — The Stars module gains anevlogoption that runsinitLoggerand adds the transport. Passevlog: true, or write the options inline (env,sampling,redact,pipeline, …) withdrainpointing to a file that default-exportsdefineEvlogDrain(...).@wolfstar/plugin-logger/evlog/pluginentry — Its default export is the plugin factory, taking the drain directly outside Stars.- Interaction wide events — The evlog plugin emits one evlog wide event per interaction (command, component, modal, and optionally autocomplete) with its outcome, error, duration, and who/where. Control it with the
interactionsoption, and add fields from a command withuseInteractionLogger(). - Sentry breadcrumbs and Logs —
SentryTransportkeeps the message and context next to an exception, can record breadcrumbs (breadcrumbLevel), and can send Sentry Logs (logLevel).
Updates
EvlogTransport— Writes structured events through evlog’s pipeline instead of flattened strings, maps all six levels, and flushes thedrainon close.SentryTransport— Flushes the client on close.WinstonTransport— Serialises errors and flagsfatalentries.
Bug fixes
WinstonTransportclose — Closing the transport twice no longer hangs.
Migration
@sentry/nodepeer dropped — The plugin no longer declares@sentry/nodeas a peer dependency.evlogpeer raised — Upgradeevlogto^2.30.0.- Custom transports —
LogPayloadnow includesmessage,error, andcontext. Update custom transports and test fixtures that build payloads by hand, or usecreateLogPayload.
0.3.0 (2026-10-05)
New features
/moduleand/pluginentrypoints — Adds@wolfstar/plugin-logger/moduleand@wolfstar/plugin-logger/plugin. List the module inmodulesinstars.config, or pass thedefinePluginfactory toplugins. Both need@wolfstar/http-framework6.1 (and@wolfstar/kitfor the module)../registeris unchanged and still supports framework v3, v5, and v6. (#187)
0.2.2 (2026-10-04)
Updates
http-framework6 support — The peer range now accepts@wolfstar/http-framework^6.0.0. (#176)
Bug fixes
- Peer range — Accept
@wolfstar/http-frameworkv6 in the peer range (|| ^6.0.0). (#176)
0.2.1
Bug fixes
- Peer dependency — Accept
@wolfstar/http-frameworkv5 as a peer dependency (^3.4.0 || ^5.0.0), so v5 projects no longer install the plugin with an unmet peer. (#125)
0.2.0 (2026-09-24)
New features
- New package — Add
@wolfstar/plugin-logger, a pluggable logger for@wolfstar/http-frameworkthat replaces the deprecated@wolfstar/logger. It installs aLoggerascontainer.loggerthrough thepreGenericsInitializationhook, implementing the framework’sILoggercontract so migrating is a drop-in change. Instead of being hardcoded toconsole, it fans every entry out to a list of transports, each able to filter by its own level on top of the logger’s. The package shipsConsoleTransport(the zero-dependency default) andSentryTransportin its core entrypoint, plusConsolaTransport,EvlogTransport, andWinstonTransportbehind the./consola,./evlog, and./winstonsubpaths. Every backend is an optional peer dependency whose instance is injected through the transport constructor, so the core stays free of runtime dependencies and consumers only install what they actually use. (#70)