fix: logger print invalid context when no stack trace provided

[JulienDuf]

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?

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

What is the current behavior?

When using the ConsoleLogger.error with two parameters, the logger will assumed that the second parameter is an Error or override of the context.

If the second parameter not a string or an Error, it will use the second parameter as the context instead of using the default context of the Logger.

Ex:

function bootsrap() {
  const logger = new ConsoleLogger('MyCustomLogger');
  logger.error('Unexpected error', { requestId: '123456' });
}

Will log

{ level: 'error', pid: 1, timestamp: 1770231457646, message: 'Unexpected error', context: { requestId: '123456' } }

What is the new behavior?

When using the ConsoleLogger.error with two parameters, when the second parameter is not an Error, the logger will fallback to the default logger logic the detect the context from the provided arguments.

function bootsrap() {
  const logger = new ConsoleLogger('MyCustomLogger');
  logger.error('Unexpected error', { requestId: '123456' });
}

Will log

{ level: 'error', pid: 1, timestamp: 1770231457646, message: 'Unexpected error', context: 'MyCustomLogger' }
{ level: 'error', pid: 1, timestamp: 1770231457646, message: { requestId: '123456' }, context: 'MyCustomLogger' }

Does this PR introduce a breaking change?

• Yes
• No

Other information

[coveralls]

Pull Request Test Coverage Report for Build f2299e45-9676-4504-a184-e3991acbf705

Details

• 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 89.829%

---

Totals
Change from base Build de840762-4bfe-4770-992b-5e40c0894ecb:	0.0%
Covered Lines:	7463
Relevant Lines:	8308

---

💛 - Coveralls

[kamilmysliwiec]

LGTM