Rethinking of the UX approach - 3 issues

[UnrulyNatives]

Thank you for your great job at creating the log viewer.
There are several issues which must be faced in order to make your work usable

1. The URL which produced the error is not shown.
This is a general issue in Laravel 12, as far as I understand. The feature worked in Laravel 10.
The issue makes it very hard to pinpoint data inconsistency which caused the error.
In general, a log-viewer should FACILITATE such task.
TODO: As the code which delivers the problematic URL is to be created outside of your package, maybe a quick extra tutorial should be added?

2. The error output is A WALL OF TEXT. 95% of it is NOT NECESSARY, as the entries refer to code which is NOT EDITABLE by the app developer (your package's user).
   In 99,9% of cases, the issue is a TYPO SOMEWHERE IN A CONTROLLER OR MODEL OR VIEW FILE.
   TODO: Therefore your user should be able to hide or change font color of all the lines which contain string vendor\\.

In other words, there is no value added that your package provides. Your user can open the log file and see a wall of text without it. What a log viewer SHOULD do is to do eliminate all unnecessary information and provide the useful.

3. Your config file is named 'log-viever.php', which is exactly the same as another package - arcanedev/log-viewer. As a result, your useer cannot test your package and use the old one at the same time. arcanedev's package seems to be abandoned, by the way. No updates for over 1 year.
   Still, with UX flaws in your package and with my own hacks to the last arcanedev package, yours is nout viable.

4. Last issue: When browsing through daily log dumps
   Now the list of daily dumps takes c. 30% of the viewport.
   Its very presence might be usefull when debugging errors from production server.
   However, in my case at least 90% work is creating code. For this type of work, the tree of daily log files is not necessary when analysing the TEXT WALL your package presents.

Thank you for your attention.