>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #760890. --> Reported by: [yesct](https://www.drupal.org/user/258568) >>> <p>Add a "modules that depend on this module" link/block to module project pages (and a link to a description for how to do that type of search from <a href="http://drupal.org/project/modules">http://drupal.org/project/modules</a>)</p> <p>I wanted to search for modules that depend on the Features module (to see what feature were available on d.o), so I made <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/webmasters/issues/760878" title="Status: Closed (fixed)">#760878: Add a "Features" term to the taxonomy vocab for modules on d.o</a></span></p> <p>but I think this is a general nice thing, like if I went to the Features module page:<br> <a href="http://drupal.org/project/features">http://drupal.org/project/features</a><br> and there would be a link or block (top 5 by usage stats, with a more link?) there for "modules who depend on Features" </p> <p>I don't know if this is related to:<br> <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/project_dependency/-/work_items/102102" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/project_dependency/-/work_items/102102</a></span><br> <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-13"><a href="https://www.drupal.org/project/drupal/issues/328932" title="Status: Needs work">#328932: Modules and partial dependencies - enhances[] and enhancedby[] field in modules' .info.yml files</a></span></p> <p>Basically it would be a good idea to have:</p> <ul> <li>a list of modules that are required to be installed in order to use a module (the "dependencies"),</li> <li>a list of modules that require a particular module (the "dependants"), see <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/drupalorg/-/work_items/3299905" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/drupalorg/-/work_items/3299905</a></span></li> <li>a list of modules that "somehow interacts" with a module (that is, "optional dependencies").</li> </ul> <p>All this data besides the optional dependencies are already stored in the .info files, we just need to pull them out and store it in the database. There are many benefits of having this data available, such as:</p> <ul> <li>informing end users what other modules they'll need beforehand,</li> <li>having a better grasp of the popularity of a "parent"/API module,</li> <li>just to see how modules in Drupal all work together.</li> </ul> <p>For the interface, a simple list like <a href="http://www.archlinux.org/packages/extra/x86_64/cups/">http://www.archlinux.org/packages/extra/x86_64/cups/</a> should be nice enough. (Optional modules can be just marked as "optional", with some remarks of why they are so.)</p> <p>Right now the maintainers use regular webpages for this, which is a tedious task for them. So, often these lists end up neglected and seriously outdated. Besides, leaving that task up to each individual project's maintainer(s) makes the placement and style of this information inconsistent across Drupal.org. These are two of the most important reasons why we should make the generation of this information an automated task and display them in a specific way (TBD) and in a specific place (also TBD) in each project's page.</p> <p>Also if this data is made public it can be used by utilities such as drush to automatically download necessary dependencies.</p> <p>PS: The one complexity is that different releases can have different dependencies. To solve that, we *could*:</p> <ul> <li>show only the dependencies of the releases that are actually shown on the project page (if we can figure that out)</li> <li>show it in the "Downloads" section (a "dependencies" link?)</li> <li>show it in an AJAXy set of tabs where each tab is a branch/major version</li> </ul> > Related issue: [Issue #3299905](https://www.drupal.org/node/3299905)