feat(common): modify Logger to allow setting a prefix

[jochongs]

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?

Issue Number: #13841

What is the new behavior?

Hello,

I became interested in this issue, so I made some methods.

As suggested in the issue (app.setLoggerPrefix('my-app-name')), I created a setLoggerPrefix method.

async function bootstrap() {
  const app = await NestFactory.create(AppModule);

  app.setLoggerPrefix('app-name');

  await app.listen(3000);
}

I expected it to be used in this way.

However, I noticed that logging also occurs when NestFactory.create is called. The prefix set with app.setLoggerPrefix does not apply to these log messages because NestFactory.create is called before app.setLoggerPrefix.

To address this, I added a loggerPrefix field to NestApplicationContextOptions, and now you can use it like this:

async function bootstrap() {
  const app = await NestFactory.create(AppModule, { loggerPrefix: 'app-name' });

  await app.listen(3000);
}

What are your thoughts on this approach? I'd appreciate your feedback.

Does this PR introduce a breaking change?

• Yes
• No

Other information

[coveralls]

Pull Request Test Coverage Report for Build 91c61ea8-273a-4e06-9317-921e6278b09a

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 92.213%

---

Totals
Change from base Build 7dd97924-96eb-4863-bad1-427333102233:	0.0%
Covered Lines:	6750
Relevant Lines:	7320

---

💛 - Coveralls

[micalevisk]

If I'm not wrong, that ConsoleLogger is public (ie., can be used by other devs to change logger formatting etc as per https://docs.nestjs.com/techniques/logger#extend-built-in-logger). And so adding a new mandatory method to it implies in a adding a breaking change. Kamil can correct me.

---

Also, just a minor opinion about this approach: to me, adding setLoggerPrefix to INestApplication interface is a bit confusing as we can use it alongside app.useLogger because we will change the same thing (the logger) in two steps. And this leaves room for adding new methods that act over the logger again, making things even worse in the future.

We can define that prefix and even change the whole presentation already like this:

class MyLogger extends ConsoleLogger {
  formatPid(pid: number) {
    return `[Foo] ${pid} - `
  }
}

// ...

app.useLogger(new MyLogger())

[jochongs]

@micalevisk

Hello, thank you so much for your feedback.

I overlooked the useLogger method. Adding a method to INestApplication that allows modifying the prefix could cause confusion with useLogger.

So, I tried a simpler approach by utilizing environment variables. What do you think about this method?

#13940

[kamilmysliwiec]

#14121