Improve error handling

[bakerkretzmar]

This PR makes some long-overdue improvements to Jigsaw's error handling. The code is mostly copied from Laravel and tweak slightly, and lots of Laravel functionality was removed so that we're only implementing what we absolutely need for now.

Highlights

• Adds an Artisan-like exception handler to give us more control over error handling.
• Installs Collision and renders errors with it, so they're now much prettier, show stack traces, and include basic syntax highlighting.
• Installs Laravel Ignition and maps Blade errors through its custom handler/compiler, so their stack traces display the original uncompiled Blade templates.

Demo

Here are before and after comparisons for a few possible error scenarios:

1. Undefined variable in Blade template

{{ $test }}

Before

Build succeeds (this is bad, it should fail), no error output in the console and no indication that anything is wrong. Additionally, the missing variable is rendered as an error visible in the HTML of the built site:

Warning: Undefined variable $test in /Users/jacob/Code/tighten/tightendotco/cache/914bb3c0cbe5c1750461e191b6c1f4a331a98ef3.php on line 2

After

Build fails with a nice-looking and detailed error message, including a stack trace pointing to the source of the error in the original, uncompiled Blade template:

2. Invalid expression / syntax error in Blade template

{{ aaaaa ->jnpa af.asdf }}

Before

Build fails with a short, ugly error message (in this case it indicates correctly where the error came from, but I've seen it get that wrong or not provide that info at all many times):

After

Build fails with a pretty, detailed error message and stack trace:

3. PHP deprecation

{{ str_contains(null, 'f') }}

Before

Build succeeds, no error messages, and the deprecation warning is rendered into the output of the site:

Deprecated: str_contains(): Passing null to parameter #1 ($haystack) of type string is deprecated in /Users/jacob/Code/tighten/tightendotco/cache/5ca2f78ccab5990f8ff2686eb4263c891fd085e1.php on line 11

After

Build succeeds, but displays warnings in the console, and the error is not rendered into the built HTML:

4. Exception thrown manually

// inside a collection helper in config.php
throw new RuntimeException('Uh oh...');

Before

After

The original source line of the exception is not visible in this screenshot. This is a small trade-off of this PR—because we're now rendering all exceptions with a lot more detail, some specific cases like this one will no longer display exactly what we need initially. The source line we're looking for here (in config.php) is frame #3, which becomes visible if you re-run the build verbosely (-v). Eventually we could fix this with our own custom exception renderer that shows more stack frames, but that feels like overkill for now.

[damiani]

Love this! 🎉

[mattstauffer]

WHOA. Love this!

[husseinalhammad]

Awesome stuff 🚀