Unable to filter module info logs from rolldown

[spalger]

Describe the bug

Our build produces thousands of chunks and as such the module listing is noise that makes our build logs illegible. We still want other "info" level logs though, so we use a customLogger to filter out the module listing reported during the build. With rolldown-vite this module listing seems to be written directly to stdout based on the log level without any capability to intercept or filter out these log lines.

Even if an API to customize logging in the same way isn't feasible, it seems like filtering raw stdout from the rust side of things would be an appreciated config option.

Reproduction

https://stackblitz.com/edit/vitejs-rolldown-vite-plgqd5yh?file=vite.config.js

Steps to reproduce

The reproduction defines all the log-related config that I understand is how you can manage this type of thing from normal vite, wrapping all log messages in an object which is logged indicating that the log messages flow through the logger.

Run npm install && npm run build

Observe that certain log messages from rolldown are not flowing through the customLogger, optimizeDeps.rolldownOptions.onLog/onwarn or build.rolldownOptions.onLog/onwarn configs.

System Info

System:
    OS: macOS 26.1
    CPU: (14) arm64 Apple M4 Pro
    Memory: 3.27 GB / 48.00 GB
    Shell: 5.9 - /opt/homebrew/bin/zsh
  Binaries:
    Node: 24.8.0 - ~/.local/state/fnm_multishells/17773_1764605948125/bin/node
    Yarn: 1.22.22 - ~/.local/state/fnm_multishells/17773_1764605948125/bin/yarn
    npm: 11.6.0 - ~/.local/state/fnm_multishells/17773_1764605948125/bin/npm
    pnpm: 10.16.1 - ~/.local/state/fnm_multishells/17773_1764605948125/bin/pnpm
  Browsers:
    Chrome: 142.0.7444.176
    Safari: 26.1
  npmPackages:
    rolldown-vite:  7.2.9

Used Package Manager

npm

Logs

Click to expand!

> vite build

(node:23) ExperimentalWarning: WASI is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
(node:23) ExperimentalWarning: WASI is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
{
  msg: '\x1B[36mrolldown-vite v7.2.9 \x1B[32mbuilding client environment for production...\x1B[36m\x1B[39m',
  options: { environment: '\x1B[90m\x1B[2m(client)\x1B[22m\x1B[39m' }
}
✓ 3 modules transformed.
computing gzip size (0)...(node:23) ExperimentalWarning: WASI is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
dist/index.html                0.13 kB │ gzip: 0.13 kB
dist/assets/index-B3077RXJ.js  0.72 kB │ gzip: 0.41 kB
{
  msg: '\x1B[32m✓ built in 194ms\x1B[39m',
  options: { environment: '\x1B[90m\x1B[2m(client)\x1B[22m\x1B[39m' }
}

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs and the Rolldown-related guide.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.