Closed shreyagarwal closed 8 years ago
The case where this occurred was when we send a massive json (but not a string) into the logger.
This is because the npmlog does a util.format before emitting the log message.
We have the option of returning from the function before it does any kind of processing but that requires change in the npmlog repo . We'll have to fork it soon .
Since this was fixed in our fork, #11 should fix this. Can you please verify?
Done. Removed log recording functionality in npmlog
If we are printing huuge number of verbose logs in production with Level set to info , then it should not take so much time. If level is not at par, then the logs should simply be discarded