Ignition tells you what to do, which is new

The error page in 6.0 does not just show a stack trace — it recognises common failures and offers a fix, and for a couple of them it will apply the fix for you.

# what it catches, among others:
#   an undefined variable in a Blade view
#   a missing .env key that a config file reads
#   a route referenced by a name that does not exist
#   an unknown Eloquent column, with the table's real columns listed

# and it is a package, so it goes in require-dev only:
$ composer require --dev facade/ignition

Keeping it out of the production dependency set matters because a debug error page in production leaks environment variables, the file layout and occasionally credentials. The APP_DEBUG check is what is supposed to prevent that, and relying on one flag being right on every host is thinner protection than simply not installing it. The solution suggestions are genuinely useful for the first month with a codebase and stop mattering afterwards, which is the right shape for a development tool.