Fix: we cannot nicely handle boot errors in custom modules as we have no framework to display them

1 files changed, 7 insertions, 5 deletions

diff --git a/app/Services/ModuleService.php b/app/Services/ModuleService.php
index 9c85eca87b..7ba90343ea 100644
--- a/app/Services/ModuleService.php
+++ b/app/Services/ModuleService.php
@@ -323,13 +323,15 @@ class ModuleService
 
                     return $module;
                 } catch (Throwable $ex) {
-                    $message = '<pre>' . e($ex->getMessage()) . "\n" . e($ex->getTraceAsString()) . '</pre>';
-                    FlashMessages::addMessage($message, 'danger');
-
-                    return null;
+                    // It would be nice to show this error in a flash-message or similar, but the framework
+                    // has not yet been initialised so we have no themes, languages, sessions, etc.
+                    throw $ex;
                 }
             })
-            ->filter();
+            ->filter()
+            ->mapWithKeys(function (ModuleCustomInterface $module): array {
+                return [$module->name() => $module];
+            });
     }
 
     /**