Should application modules be moved to composer packages?

Question

PHP

Task: optional connection of system modules, taking into account versioning, updating modules.
If, for example, we take into account libraries that are not related to the application level, everything is fine here, we connect via composer and use it, the library is tested, stable.
But if we take into account, for example, a part of the application expressed as a module that contains functionality that extends the base one, these are some interface elements, pages of the administrator part, views, etc.
For example, a sitemap.xml sitemap generation module that has a certain admin page with module settings, several controllers, configs. Which in turn is tied to the sitemap_generator library.
How to proceed, either using both packages through composer and composer will allow you to update dependencies between packages, or leave the library in composer and install the module in the main application through some kind of installer?

Answer 1

Costs. Here is an example of a similar solution for Yii2. There is no need to add a dependency on sitemap_generator to the application if the module under development already has it.