fix(common): Single stdout.write() call per logging in default Logger

[ulrichb]

This fixes the issue that in PM2 (at least when running in Windows) the logging lines break at the "stdout.write() border".

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior?

The default LoggerService multiple times calls process.stdout.write() per logging line. This seems to confuse the process manager PM2's logging system (the full logging message is split into 2 or more parts).

An example screenshot:

What is the new behavior?

I've refactored printMessage() so that it concatenates the logging string first and then calls process.stdout.write() once. Same in printStackTrace().

Note that other than this there should be no change of the behavior.

... and this fixes my issue with PM2:

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

[coveralls]

Pull Request Test Coverage Report for Build 6696

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 95.311%

---

Totals
Change from base Build 6687:	0.0%
Covered Lines:	4391
Relevant Lines:	4607

---

💛 - Coveralls

[BrunnerLivio]

LGTM

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.