2.0.0 Use nestjs-context instead of custom one

• Huge breaking change to use nestjs-context library instead of using custom Context.
• Simplified naming: LoggerModule is the standard pino-stackdriver module and PinoContextLoggerModule is a more generic one.
• Only one "LoggerService" instead of two, so every PinoContextLogger used in 1.x must be renamed to "Logger".

Dynamic correlation-id

Refactoring to avoid using deprecated pino config options
Dynamic correlation-id so it can be used with processors

1.1.2

CI/CD - Npm publish

Bug fixed: default logger is now exported

1.1.1

1.1.1

1.1.0

Logger can be used now as Application or Application + Initialization logger through two different helpers: createStackdriverLoggerTool and createLoggerTool.

1.0.0 AKA The Fantastic Five

This package includes:

nestjs-ps-tools: @BuildDto and other first-class tools to be used in any Nestjs project
nestjs-context: A Map-like Context service that can be used anywhere in your application
nestjs-correlation-id: A middleware that auto-generates a correlation id if it does not exist and exports decorators to get it
nestjs-gcloud-trace: A service to manage GcloudTrace and a middleware to add trace info (url) to the context storage and (id) to the headers
nestjs-pino-context: A pino-logger service that allows to log custom labels (from env, request or context storage), the correlation id and the gcloud trace

A Logger implementation of the nestjs-pino-context logger service configured for Stackdriver