>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3565547. --> Reported by: [phenaproxima](https://www.drupal.org/user/205645) Related to !736 >>> <p>For local development, and on CI, we almost always need to install our own packages (drupal_cms_WHATEVER) from local sources, rather than from packages.drupal.org.</p> <p>Right now, we have a few ways of doing that. On CI, we create an artifact repository; locally, we have global path repositories. Both approaches run a risk of colliding with packages.drupal.org and installing the wrong thing.</p> <p>Composer provides a way out, which is the <code>only</code> and <code>exclude</code> configuration options: <a href="https://getcomposer.org/doc/articles/repository-priorities.md">https://getcomposer.org/doc/articles/repository-priorities.md</a>. These allow certain packages to <em>never</em> be loaded from that repository.</p> <p>This might be a really good approach for us. By explicitly forcing certain packages which are on packages.drupal.org to be loaded from local sources, we can ensure we're always consistently loading packages from where we expect.</p>