feat: Support ESM logging module #775
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #760
I also want to add support for taking the logger from the main plugin module instead, in the same way you can specify an options object as a named export on it when giving the– This already exists as--optionsflag. But I haven't decided on how to name the CLI flag and if it should have a short single letter alias. Any suggestions?options.loggerwith--optionsenabled. But there is an issue withdeepmergeand passing an already createdpino.Logger.Checklist
npm run testandnpm run benchmarkand the Code of conduct