build(deps): bump loglayer from 8.5.0 to 9.1.1

[dependabot]

Bumps loglayer from 8.5.0 to 9.1.1.

Release notes

Sourced from loglayer's releases.

loglayer@9.1.1

Patch Changes

• #383 5fcc12f Thanks @​theogravity! - Fix transport id property not being set from config

  When creating a transport with id: "file", the id property was always set to a generated value instead of the configured value. This caused group-based routing to fail because _shouldTransportReceiveLog couldn't match the transport's ID against the group's transports list.

  Before: this.id = Date.now().toString() + Math.random().toString() After: this.id = config.id ?? (Date.now().toString() + Math.random().toString())

• Updated dependencies [5fcc12f]:

  • @​loglayer/transport@​3.0.3

loglayer@9.1.0

Minor Changes

• #355 c022bb1 Thanks @​theogravity! - feat: add groups for routing logs to specific transports by named category. Inspired by categories in LogTape.

Patch Changes

• Updated dependencies [c022bb1]:
  • @​loglayer/shared@​4.1.0
  • @​loglayer/context-manager@​2.0.2
  • @​loglayer/log-level-manager@​2.0.2
  • @​loglayer/plugin@​3.0.2
  • @​loglayer/transport@​3.0.2

loglayer@9.0.1

Patch Changes

• #353 f9b32cd Thanks @​theogravity! - Log methods now return void by default instead of void | Promise<void>. Only when async lazy values are present in metadata do log methods return Promise<void>. This fixes @typescript-eslint/no-floating-promises lint errors for users not using async lazy.

• Updated dependencies [f9b32cd]:

  • @​loglayer/shared@​4.0.1
  • @​loglayer/context-manager@​2.0.1
  • @​loglayer/log-level-manager@​2.0.1
  • @​loglayer/plugin@​3.0.1
  • @​loglayer/transport@​3.0.1

loglayer@9.0.0

Major Changes

• fc56d4b Thanks @​theogravity! - - Add lazy evaluation for dynamic context and metadata using the lazy() function. Lazy values are only evaluated when the log level is enabled, avoiding unnecessary computation for disabled log levels. This feature is adapted from LogTape's lazy evaluation. Thank you to the LogTape team for answering questions around its implementation!

  • lazy() supports async callbacks in metadata for values that require asynchronous operations (database queries, API calls, async storage). When async lazy values are present in metadata, log methods return Promise<void> so you can await the log call to ensure values are resolved before dispatch. Async lazy is not supported in context.
  • getContext() now resolves lazy values by default. Use getContext({ raw: true }) to get the raw lazy wrappers.
  • Failed lazy callbacks now replace the value with "[LazyEvalError]", still send the original log, and emit a separate error-level entry describing the failure. The LAZY_EVAL_ERROR constant is exported for programmatic detection.
  • Added LogLevelPriority and LogLevelPriorityToNames exports for mapping between log levels and their numeric priority values.

  There are no breaking changes. No migration steps are necessary aside from upgrading any external loglayer dependencies to their next major version.

... (truncated)

Changelog

Sourced from loglayer's changelog.

9.1.1

Patch Changes

• #383 5fcc12f Thanks @​theogravity! - Fix transport id property not being set from config

  When creating a transport with id: "file", the id property was always set to a generated value instead of the configured value. This caused group-based routing to fail because _shouldTransportReceiveLog couldn't match the transport's ID against the group's transports list.

  Before: this.id = Date.now().toString() + Math.random().toString() After: this.id = config.id ?? (Date.now().toString() + Math.random().toString())

• Updated dependencies [5fcc12f]:

  • @​loglayer/transport@​3.0.3

9.1.0

Minor Changes

• #355 c022bb1 Thanks @​theogravity! - feat: add groups for routing logs to specific transports by named category. Inspired by categories in LogTape.

Patch Changes

• Updated dependencies [c022bb1]:
  • @​loglayer/shared@​4.1.0
  • @​loglayer/context-manager@​2.0.2
  • @​loglayer/log-level-manager@​2.0.2
  • @​loglayer/plugin@​3.0.2
  • @​loglayer/transport@​3.0.2

9.0.1

Patch Changes

• #353 f9b32cd Thanks @​theogravity! - Log methods now return void by default instead of void | Promise<void>. Only when async lazy values are present in metadata do log methods return Promise<void>. This fixes @typescript-eslint/no-floating-promises lint errors for users not using async lazy.

• Updated dependencies [f9b32cd]:

  • @​loglayer/shared@​4.0.1
  • @​loglayer/context-manager@​2.0.1
  • @​loglayer/log-level-manager@​2.0.1
  • @​loglayer/plugin@​3.0.1
  • @​loglayer/transport@​3.0.1

9.0.0

Major Changes

• fc56d4b Thanks @​theogravity! - - Add lazy evaluation for dynamic context and metadata using the lazy() function. Lazy values are only evaluated when the log level is enabled, avoiding unnecessary computation for disabled log levels. This feature is adapted from LogTape's lazy evaluation. Thank you to the LogTape team for answering questions around its implementation!

  • lazy() supports async callbacks in metadata for values that require asynchronous operations (database queries, API calls, async storage). When async lazy values are present in metadata, log methods return Promise<void> so you can await the log call to ensure values are resolved before dispatch. Async lazy is not supported in context.
  • getContext() now resolves lazy values by default. Use getContext({ raw: true }) to get the raw lazy wrappers.

... (truncated)

Commits

• 437ec66 chore: release package(s) (#384)
• 5fcc12f fix(transport): use config.id instead of always generating one (#383)
• b5b74bd docs: restore Theo Gravity link in attribution
• ee302b7 docs: update copyright to Theo Gravity / Disaresta (2026)
• 4410f09 chore: release package(s) (#356)
• 036fd2c chore: update devdeps
• c022bb1 feat: add groups for routing logs to specific transports (#355)
• f3f62e6 chore: release package(s) (#354)
• f9b32cd fix: conditional void/Promise<void> return types for log methods (#353)
• 3b906ce chore: release package(s) (#351)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for loglayer since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Dependabot attempted to update this pull request, but because the branch dependabot/npm_and_yarn/loglayer-9.1.1 is protected it was unable to do so.