Reopen: #56865

The Problem

When a package like spatie/laravel-ignition is installed, it provides its own ExceptionRenderer. However, the framework's default exception listener is still registered alongside it. This causes every exception to be handled twice, resulting in redundant work and unnecessary memory usage (e.g., populating $queries when it is not needed).

Simple Recreation

1. Install spatie/laravel-ignition in a fresh Laravel project.

   composer require spatie/laravel-ignition

2. Create a route that throws an exception:

   // routes/web.php
   Route::get('/test-exception', fn() => throw new Exception('test'));

3. Temporarily add a dd() to the framework's default listener to see it run:

   // In vendor/laravel/framework/src/Illuminate/Foundation/Exceptions/Renderer/Listener.php:73
   // Inside the Listener class, method onQueryExecuted()
   public function onQueryExecuted(QueryExecuted $event)
   {
       if (count($this->queries) === 100) {
           return;
       }
   
       $this->queries[] = [
           'connectionName' => $event->connectionName,
           'time' => $event->time,
           'sql' => $event->sql,
           'bindings' => $event->bindings,
       ];
   
       dd($this->queries); 
   }

4. Access /test-exception in the browser. You will see the dd() message, proving the default listener ran when it shouldn't have.

The Solution

This PR adds a check (! $this->app->bound(ExceptionRenderer::class)) to ensure the default listener is only registered if no other ExceptionRenderer has already been bound to the container. This cleanly prevents the duplication.

Tests

• Added test to ensure listeners are not registered if ExceptionRenderer exists.
• Added test to ensure listeners are registered if ExceptionRenderer does not exist.