-
-
Notifications
You must be signed in to change notification settings - Fork 6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Too long error messages get cropped #17632
Comments
Hello @paulwer. Please provide a minimal reproduction using a GitHub repository or StackBlitz. Issues marked with |
Not possible, because this would be a big repo, with 1000s files. The edge case is described sufficient. |
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. |
yes, thats the part of the logger resulting in this behavior. |
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. |
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
Used Package Manager
npm
Logs
Error: Failed to scan for dependencies from entries:
...and x more lines
Validations
The text was updated successfully, but these errors were encountered: