Closed devceline closed 6 months ago
[!NOTE] Canary of this fix already published at: @walletconnect/logger@2.1.2-98c4166
@walletconnect/logger@2.1.2-98c4166
1.11.1
Writable
DestinationStream
"resolutions": { "@walletconnect/logger": "2.1.2-98c4166" },
npm-force-resolutions
@walletconnect/logger
The current tests already use the ServerChunkLogger so them passing indicates that behaviour is effectively unchanged
ServerChunkLogger
How was this reproduced
1.11.1
How was this fixed
Writable
DestinationStream
interfaceHow was this tested
Ensure it resolves issue
npm-force-resolutions
to force@walletconnect/logger
's canary to be fetched instead of the current latestEnsure test pipeline passes
The current tests already use the
ServerChunkLogger
so them passing indicates that behaviour is effectively unchanged