Added a new Community Transport option to the list: Worker Thread based async Console Transport #2140
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
arpad1337
force-pushed
the
transports/worker-thread-based-async-console-transport
branch
from
57d9e74
to
7993314
Compare
arpad1337
changed the title
This was referenced May 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The new
ConsoleTransportInWorkerextension on top ofwinston.transports.Consoleis leveraging the power of NodeJS v16'sworker_threadsmodule to offload expensive & blocking write operations to a separate thread with its own Event Loop while keeping the main thread high performant and its Event Loop non-blocked.Code on GitHub
NPM Package