>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #2474007. --> Reported by: [klausi](https://www.drupal.org/user/262198) Related to !32 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>In Drupal 8 modules will depend more and more on independent PHP components (libraries that are not modules). Example: Payment module and Rules module will both depend on a PluginSelector shared library. Ideally we want to host that library on drupal.org for visibility reasons. The components will be pulled in by Composer.</p> <p>drupal.org only has modules, themes and distributions as project type, so we should ad another type because we don't want that components to show up in module search results for example. </p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Add a node type for components on drupal.org. There should be no special configuration to make it discoverable by Composer and Packagist, we are doing that already for <a href="https://www.drupal.org/project/coder">Coder</a> (<a href="https://packagist.org/packages/drupal/coder">home at Packagist</a>) for example.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <p>Decide on a name, current proposal "Component project".</p> <p>The description could then be nearly the same as @drumm's draft: </p> <blockquote><p>General projects are all other projects that are not Drupal modules, themes, or other more-specific project types. For example, JavaScript components, Drush extensions, and libraries.</p></blockquote> > Related issue: [Issue #2401519](https://www.drupal.org/node/2401519) > Related issue: [Issue #1826054](https://www.drupal.org/node/1826054) > Related issue: [Issue #1856762](https://www.drupal.org/node/1856762) > Related issue: [Issue #2002304](https://www.drupal.org/node/2002304)