One module => One panel ?

[felahdab]

Hi.
I have a set of modules that each register a service provider which extends PanelProvider and which defines a filament panel. 1 module => 1 panel.

With Laravel 10, nwidart 10 and coolsam 3, everything is fine. I can see all my panels.

After upgrading to laravel 11, coolsam 4, nwidart 11, the panels are not registered anymore (not appearing in Filament::getPanels(), no route registered either).

But the PanelProvider register($panel) is called, and the corresponding callback IS registered intro the application...

I suspect this has something to do with registering and booting order because when I refresh the PanelRegistry singleton from tinker, Filament::getPanels() correctly shows all my panels.

I would be glad to get some hint on what has changed and how to fix it.

Regards.
Florian.

[felahdab]

Hi again.

I finally figured it out.
My issue was solved by preventing auto loading of nwidart/laravel-modules and filament/filament services providers, and registering them manually in config/app.php, first the modules, then Filament.

Now I have modules which each expose a Filament panel.

Hope this can be helpful for others.

Regards.
Florian.