Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
When you get an "ErrorException (E_ERROR)" which is as a result of something in the view being wrong. Following down the exception you get presented with the view that's causing the issue but it's always the cached view:
storage/framework/views/1b6e1ae14d9f2354504bf504d3d51c19bee64adc.php:37
Ok so it's not a huge deal, I'm more than capable of finding that file (thought the line the error is on maybe not be the same as my "views" file prior to caching.
I just wondered if it were possible to make the error message reflect the line causing the issue in
/assets/views/bad_view.blade.php
just an idea and it may be possible already (if it is I don't know how to change it though).
Cheers
the cached view can include other views and even repeated ones so the line number has no relation to the source file
To trace it back would probably need some form of source map which could be expensive to build each time a new view cache is required ?
@snapey That does make a lot of sense.
I wonder if (though I appreciate difficult), a composer package would work for dev then you turn it off for live.
That way the overheads wouldn't be an issue?
Please or to participate in this conversation.