Build writes normal output to stderr

[kaiyoma]

Describe the bug

A VitePress build is writing normal (non-error) messages to stderr. This causes other tools (like Rush) to interpret the build as failing.

Reproduction

$ npx vitepress build> stdout.txt
✓ building client + server bundles...
✓ rendering pages...

Expected behavior

Non-error messages written to stdout.

System Info

System:
    OS: Windows 11 10.0.26100
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz
    Memory: 4.87 GB / 15.71 GB
  Binaries:
    Node: 22.14.0 - C:\Program Files\Node.js\node.EXE
    npm: 11.1.0 - C:\Program Files\Node.js\npm.CMD
  Browsers:
    Edge: Chromium (131.0.2903.86)
    Internet Explorer: 11.0.26100.1882
  npmPackages:
    vitepress: 1.6.3 => 1.6.3

Additional context

No response

Validations

• Check if you're on the latest VitePress version.
• Follow our Code of Conduct
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

[brc-dd]

You can configure rush to change the behavior - microsoft/rushstack#1329 (comment)

We can fix this in vitepress too and vitepress' output isn't consistent but IMO rush isn't right either. Also, not sure what to do with spinner when it actually fails.

Running spinners on stderr is a common practice:

sindresorhus/ora#85 (comment)

Other examples -

vuejs/vue-cli#4389 (comment)
sloria/konch#66 (comment)
denoland/deno#25114

But one can argue that the main reason for doing that is allow piping which one won't be doing with vitepress anyway.

[kaiyoma]

Oh cool, I didn't know about that Rush setting. Thanks! (I ended up working around this by piping stderr to stdout when running the VitePress build.) Feel free to close this if it's a WONTFIX.

[brc-dd]

I'm keeping this open for now. Let's see if there are better suggestions. A logger refactor is planned. Will see what to do with this then. Feel free to unsubscribe from the right sidebar. 👍