Ability for filter by "Not Required module"

Not sure how to calculate not required modules. But the scenario you're describing have you looked into https://www.drupal.org/project/config_split → , having a non-prod split.

I have splits for local, migration, dev, stage, prod which install certain modules.

hi
i am already using config_split in the scenario you describe . but it means that you must know exactly what you are doing after investigating on each module implication

As you can see at admin/module page with module_filter enabled you can filter by Enabled, disable, Unavailable .

My request about "Not required" module because i have seen that for each module listed at admin/module page there is an info (**Required by:**) saying if it's actually required by another module . So i was expecting with my feature request there could be a **Not required** filter that will exclude from the list modules **actually required**

The https://www.drupal.org/project/unused_modules → looks to be doing something similar but there is a lot of confusion there

Sounds like a core request, but don't see how that would be calculated on the fly.

But believe to be out of scope of this module.

@delacosta456 just so we understand what you are asking for: The "required by" means that the module is needed by another module in the list. If we could filter out and show just the modules that did have a "required by" I am wondering how that would be useful? Some of those modules would be needed, as standalone modules, and some might still not be needed at all. Is that what you were meaning?

It might be possible to do that within this module, we could use the presence/absence of the Required by: text in the dropdown info div.

Thinking about this again, we cannot simply add a new single checkbox because most of the time we would want to see the modules regardless of whether are required or not. The existing set of three checkboxes (enabled, disabled, unavailable) work as a unit, and each module is considered to be in one and only one of those categories. So ticking all three boxes shows the modules. For the potential new ones, we would need two checkbox (required by another module, not required by another module) then ticking just one of them would show that subset of the modules (also respecting the other 3x checkbox settings).

Another solution to this might be to add the "required by:" and "requires:" form elements into the set of things that the normal filter searches on. That would give you the same functionality, but might be more powerful too. It might allow filtering on a module name to show which others are required by it, for example. That is potentially much more useful and generic.