Date Published: April 22, 2022

Ebwh-049 [verified]

As we continue to navigate the vast expanse of the internet and uncover new information, it's essential to approach codes and keywords like EBWH-049 with a critical and nuanced perspective. By doing so, we can separate fact from fiction, identify patterns and connections, and potentially uncover new knowledge and understanding.

Composer allows you to "require" a set of dependencies that it "installs." Again, in Composer parlance, “install” simply means that the Composer package will be downloaded and correctly loaded (made available to PHP classes) by the Composer autoloader.

To use Composer to "install" a new Drupal project (module, theme, profile, etc.), execute:

 composer require drupal/[project-name]

Where [project-name] is the machine name of the project (module, theme, distro, etc.) on Drupal.org. You can always find the machine name of a Drupal project on it’s project page on Drupal.org:

For instance, to require token, execute:

 composer require drupal/token

This will add drupal/token to the require array in your composer.json. It will choose a default version constraint based on your composer.json configuration. E.g., if you have specified "prefer-stable": "true" then this will download the latest stable version of the package.

You may also specify the version constraint by adding second argument:

 composer require drupal/token ^1.1.0

Make sure to commit the changes to composer.json and composer.lock after requiring the new module. As mentioned above and in How to Structure Your Drupal Repository, the Drupal module files will not be committed to Git. Rather, Composer will read the contents of composer.lock when installing or deploying your site to another environment in order to install the expected packages.

To update drupal/token and require a new version constraint (such as 1.10), execute:

 composer require drupal/token:^1.10 --update-with-all-dependencies

Authored By: Matthew Grasmick, Senior Director of Product