Oh Dear is the all-in-one monitoring tool for your entire website. We monitor uptime, SSL certificates, broken links, scheduled tasks and more. You'll get a notifications for us when something's wrong. All that paired with a developer friendly API and kick-ass documentation. O, and you'll also be able to create a public status page under a minute. Start monitoring using our free trial now.
If you execute an Artisan command and something goes wrong, the error output is not terribly detailed.
You can improve the output slightly by tagging on -vvv to make to output more verbose.
Now we already know the line that where the problem originates: there's something going wrong on line 41 of the MyBrokenCommand command.
But we can improve the error output still. Nuno Maduro coded up a fantastic package called Collision that, once installed, provides much nicer output.
In this output we can immediately see what the silly programmer did wrong.
Let's hope that a future version of Laravel will be able to spit out these nicely formatted errors out of the box.
You can follow me on these platforms:
On all these platforms, regularly share programming tips, and what I myself have learned in ongoing projects.
Every month I send out a newsletter containing lots of interesting stuff for the modern PHP developer.
Expect quick tips & tricks, interesting tutorials, opinions and packages. Because I work with Laravel every day there is an emphasis on that framework.
Rest assured that I will only use your email address to send you the newsletter and will not use it for any other purposes.
What are your thoughts on "Improve the error output of console commands in a Laravel app"?