Skip to content

@loglayer/shared Changelog

3.0.1

Patch Changes

  • fa69748 Thanks @theogravity! - Add optional disposable method to the IContextManager and ILogLevelManager interfaces. They've always supported it, but it was not explicitly noted for the interface.

3.0.0

Major Changes

  • #305 5af0d6b Thanks @theogravity! - New version 8 of LogLayer introduces Log Level Managers, a system for managing log level settings across logger instances. Log level managers provide a way to control how log levels are inherited and propagated between parent and child loggers.

    v8 does not have any breaking changes; no migration steps are necessary to upgrade from v7 -> v8 of loglayer.

2.7.1

Patch Changes

2.7.0

Minor Changes

2.6.0

Minor Changes

  • 8554479 Thanks @theogravity! - Add getConfig() method to LogLayer to get the user settings used when creating the instance.

2.5.3

Patch Changes

2.5.2

Patch Changes

  • aa0d9e1 Thanks @theogravity! - Remove the LogLayerContext and LogLayerMetadata extension from the LogLayerData interface as context and metadata fields are user-configured, which the extension wouldn't capture. It now extends the Record instead.

2.5.1

Patch Changes

2.5.0

Minor Changes

  • #261 9b32187 Thanks @theogravity! - - Added new raw() method for advanced logging scenarios

    • Allows bypassing the normal LogLayer API to directly specify all aspects of a log entry

    • Supports complete control over log level, messages, metadata, error, and context

    • Still processes through all LogLayer features including plugins, context merging, and transport routing

    • See Basic Logging documentation for usage examples

    • Fixed bug where errorFieldInMetadata option was not working correctly

      • Error objects were not being placed in metadata fields when errorFieldInMetadata was set to true
      • Now properly places errors in metadata fields as specified by the configuration

2.4.0

Minor Changes

  • #239 12ca18a Thanks @theogravity! - - Transports now additionally receive the error, metadata, and context data in the shipToLogger() callback. * It is still recommended to use data for most use-cases as it is a merged object of all data with the user's configured fields.

    • Plugin callbacks onBeforeDataOut() and shouldSendToLogger() now additionally receive the error, metadata, and context data.

    This change should allow a plugin or transport developer to inspect data without needing to know how the user has configured their data object.

2.3.1

Patch Changes

2.3.0

Minor Changes

  • #190 818bae5 Thanks @theogravity! - Adds new log level control methods to ILogLayer and adds the LogLayerType type.

2.2.1

Patch Changes

2.2.0

Minor Changes

2.1.1

Patch Changes

2.1.0

Minor Changes

  • #153 96a5c57 Thanks @theogravity! - Updates around context and metadata handling.

    • Added clearContext() to clear context data.
    • withMetadata() / metadataOnly() / withContext() now allows an empty value. Empty values will not result in any data mutations or plugin executions.

2.0.0

Major Changes

  • #151 5f1260b Thanks @theogravity! - - New in v6: Context Manager implementation
    • Breaking: Removes linkParentContext option from loglayer configuration

1.3.0

Minor Changes

  • #143 733ba8f Thanks @theogravity! - Move the plugin types to the shared package to support the new withFreshPlugins() method on ILogLayer, expose plugin-only types from shared package to plugin package.

1.2.1

Patch Changes

  • #140 d708ff7 Thanks @theogravity! - Fix metadataOnly typescript def. The second parameter should always be optional.

1.2.0

Minor Changes

1.1.0

Minor Changes

  • #129 d8054c8 Thanks @theogravity! - LogLayer now passes the loglayer instance as the last parameter to all plugin callbacks

1.0.5

Patch Changes

1.0.4

Patch Changes

1.0.3

Patch Changes

1.0.2

Patch Changes

1.0.1

Patch Changes

1.0.0

Major Changes