then keys are necessary

we don't want to lose the ability

In addition this order (app first) is needed for events too

It is not so critical but it will be better when the listeners defined in the main app will be executed before packages listeners

👍

I think providers should be in their own package and only should be in modules.

I think the same, but at least the configuration for now will be simpler, here we go day by day.

For what reason providers should be in modules only?

I think not only modules but any packages.

just the settings.

@yiiliveext if we add the providers to all the packages, the composer-plugin in which order will they be placed?

so I think that if we should generate an id, to tell the composer-plugin the order in which it should be built.

the other solution would be to register all the providers in all the packages without registering them in provider.php and then if the developer needs it, add the configuration in the correct order, I lean towards this option.

We can put a default configuration in order, and the developed one activates or deactivates it.

You can rearrange providers in the main app providers.php if you want another order

👍

well I think with this the configuration will now be clearer for everyone.

@yiiliveext It is more thinking the configuration of Providers is the configuration of the modules we would only need to pass the urls more cleanly.

for now:

class AppRouterFactory
{
   public function __invoke(ContainerInterface $container)
   {
       $routes = require Builder::path('routes');

       $collector = $container->get(RouteCollectorInterface::class);
       $collector->addGroup(
           Group::create(null, $routes)
               ->addMiddleware(FormatDataResponse::class)
       );

       return new UrlMatcher(new RouteCollection($collector));
   }
}

https://bulma.io/ Framework css with SASS its awesome.