docs: added custom logger info

[g4rry420]

Signed-off-by: GurkiranSingh [email protected]

Description

Added the information about Custom Logger. Please, let me know if you see any errors :)
Resolves #9597

Additional context

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the Commit Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

[sapphi-red]

Thanks!

[patak-dev]

Thanks for the PR @g4rry420! @antfu exposed the logger so the community could reuse it. Maybe we could document changing the prefix instead? (see original PR #2019)
If we want to promote the use case described in this docs addition I wonder if we should extend before createLogger APIs to make this scheme easier.

[g4rry420]

@patak-dev What do you think of this example ?

import { createLogger, defineConfig } from 'vite';

const logger = createLogger("warn", { prefix: "[VITE-WARNING]", allowClearScreen: false });
const originalWarning = logger.warn;
logger.warn = (msg, options) => {
  if (msg.includes('vite:css') && msg.includes(' is empty')) return;
  originalWarning(msg, options);
};

export default defineConfig({
  customLoger: logger,
});

[bluwy]

I think it's fine to document this for now even with it's slightly un-ergonomic API to customize it so that others know how to filter out certain warnings.

I've also moved it as a config options docs instead which I think is a bit more fitting, but happy to discuss further too.