As part of Laracon EU 2019, Freek Van der Herten and Marcel Pociot announced their latest open-source package, Ignition.
Ignition is the new default error page for Laravel 6.0, and has some beautiful Laravel-specific features that should make debugging exceptions and stack traces significantly better! You might even enjoy throwing an exception on purpose to see this beautiful new debugging stack for Laravel.
From Freek’s detailed writeup announcing Ignition, he mentions how Ignition can do some interesting framework-specific things and make the stack trace easier to digest:
Ignition is a Laravel-specific error page. So, it can hook into framework-specific functionality to display the uncompiled view path and your blade view…we also only display the application frames by default because those are the frames you’re probably interested in.
As you can see in the screenshot, there are multiple tabs with helpful hints about the request, the app/framework, user, context, and debug. Check out Freek’s writeup for detailed information on each.
The debug tab has a cool feature of showing queries, logs, and dumps. When a dump occurs, Ignition displays the filename where the dump statement happened. No more searching for the missing
dd() call in a vendor package!
Apart from the debug information, Ignition goes the extra step trying to make suggestions to common problems. For example, a class or view path typo will try to provide suggested solutions.
Ignition is the default for Laravel 6.0, and you can install it to work with existing Laravel 5 applications. You can learn more about this package, get full installation instructions, and view the source code on GitHub at facade/ignition.