π I'm proud to share that our team has released a new major version of Ignition. It's the most beautiful error page you ever seen, and it will be the default in @laravelphp 9
πYou can also install it in Laravel 8!
𧡠Let's take a look at all the features
At the top there's a new Docs item which will go straight to the Laravel documentation. That red dot means we found a very specific page (for instance the Eloquent page for query errors)
Settings can now be saved right in Ignition itself, you don't have to edit a config file.
π YES! We do have a dark mode! π
Of course, Ignition still can fix common problems for you, such as generating a missing app key.
We always keep displaying the exception message. Take a look at this beautiful animation to make it sticky.
Ignition can now highlight Blade views correctly. We've gone the extra mile and created a Blade language file for highlight.js. You'll find it in this repo: github.com/spatie/highligβ¦
Ignition can show you the location of your dump message. Click on that path to go straight to that file.
π Ignition will also show you executed queries, and even show you the execution time. Nice!
π You can still get help from a colleague by sharing your Exception via flareapp.io, the best exception tracker for Laravel application.
π In the next few weeks, we'll also update Flare with the new Ignition design and also launch a beautiful new marketing page.
π The new version of Ignition will ship with Laravel 9, but you can also install it in Laravel 8. In composer.json just replace facade/ignition with spatie/laravel-igntion ^1.0
That's an easy upgrade of your error page.
You can now install Ignition into non-Laravel applications as well. It's one liner:
Creating Ignition was team work: @willemvbockstal created the design, @alex_ and @AdriaanMrn worked on the front end (the front end is written in React π ) Together with @alex_, I took care of the PHP packages.
πAnd a big thank you to the entire community!
Want to know more about the newest version of Ignition?
A domain is basically a way of grouping the logic of some parts so that you can work on that small parts without having to deal with all classes in your app.
It's sound heavy but it's actually a pretty lightweight practice. We talk about it in our book: laravel-beyond-crud.com
The "stick close to the default structure" mantra is the result of people who tried to go too far by putting stuff outside of the app directory, requiring service providers, splitting up resources/config directories.
When refactoring to domains, you're only changing a namespace.