Now that this is an npm package (as opposed to a standalone application), it does not make as much sense for it to have .env driven logging.
We should instead look into exposing an API that lets a user of the package define a custom logger, similar to what kafkajs does.
The log levels are already exposed in @tvkitchen/base-constants, and the countertop elements already take in settings on construction, so we're actually partly there.
What is less clear to me is if we should remove winston from the project, and if so, should that be part of this issue. Use of winston as the default might be a little opinionated / overkill as opposed to some kind of trivial console based logger default.
Task
Description
Now that this is an npm package (as opposed to a standalone application), it does not make as much sense for it to have
.envdriven logging.We should instead look into exposing an API that lets a user of the package define a custom logger, similar to what kafkajs does.
The log levels are already exposed in
@tvkitchen/base-constants, and the countertop elements already take in settings on construction, so we're actually partly there.What is less clear to me is if we should remove winston from the project, and if so, should that be part of this issue. Use of winston as the default might be a little opinionated / overkill as opposed to some kind of trivial console based logger default.
Relevant Resources / Research
Related Issues
None.