Check log.length when evaluating "legacyness" of transports #1340
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.
In
winston@3
this code inle_node
would not result in theLogentriesTransport
being wrapped in aLegacyTransportStream
becausewinston.Transport
will berequire('winston-transport')
and notrequire('winston-compat').Transport
as we expect.To work around this we now also check the function
length
of thelog
function to ensure a length of two. This is not a perfect check, but it should handle the 80% case.Related: #1280, winstonjs/winston-transport#23