I'm currently organising Full Stack Europe. It's a conference in Antwerp, Belgium for developers who want to learn across the stack. You can use this link get your ticket with a nice discount.
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
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.
Every two weeks 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.