Too long error messages get cropped

[paulwer]

Describe the bug

Hi, we encountered a error message while performing optimizeDeps feature.
Here was an error and vite listed all files of the repo. The messages contained informations what failed at the end, but the end was cropped by this feature.

Because of the crop feature we are not able to read the error.

Reproduction

no reproduction url

Steps to reproduce

No response

System Info

System:
    OS: Windows 11 10.0.22621
    CPU: (12) x64 12th Gen Intel(R) Core(TM) i7-1255U
    Memory: 1.11 GB / 15.64 GB
  Binaries:
    Node: 18.19.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.2.3 - C:\Program Files\nodejs\npm.CMD
    pnpm: 8.14.0 - C:\Program Files\nodejs\pnpm.CMD
  Browsers:
    Edge: Spartan (44.22621.1555.0), Chromium (126.0.2592.68)
    Internet Explorer: 11.0.22621.1

Used Package Manager

npm

Logs

Error: Failed to scan for dependencies from entries:

...and x more lines

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
• 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.

[github-actions]

Hello @paulwer. Please provide a minimal reproduction using a GitHub repository or StackBlitz. Issues marked with needs reproduction will be closed if they have no activity within 3 days.

[paulwer]

Not possible, because this would be a big repo, with 1000s files. The edge case is described sufficient.

[bluwy]

Do you mean #16581?

The bug that caused it seems to be fixed upstream at alexeyraspopov/picocolors#64, so maybe we can revert our fix here.

[paulwer]

yes, thats the part of the logger resulting in this behavior.

[bluwy]

I think it wasn't clear what the truncation look like in the logs given, and the logs section was easily missed in the description. Hence a repro would be helpful for others not familiar with this behaviour.

Anyways, with the issue pinpointed, feel free for anyone to fix this.