Composer

If you install a Drupal module that requires an external JavaScript library, you are more or less left on your own how to get the library into your project. If you manage your site with Composer, manually downloading and extracting packages is one of the things you wanted to avoid. Learn how Asset Packagist helps you to avoid it.

We updated all our D8 and D9 sites to use Composer 2. Composer 2.0 was released on 24 October, 2020. It is so much faster and uses far less memory. It's a big relief to remove Composer wait time from our development process not to talk of making sure there is enough high memory for Composer on our machines.

As from version 8, Drupal recommends using Composer to manage dependencies. This has thrown off users who are not comfortable working in the command line. But using Composer to manage packages in Drupal is not explicitly required, it is only a recommendation. You can still manage Drupal version 8 and upwards just the way you managed version 7 being downloading and installing from tarball or installing with Softaculous - these methods are still valid with Drupal. But what if you started manually and now you want to switch over to Composer? Hop on the link and get the info on this.

Drupal 8 and above recommends using Composer to manage Drupal sites. From initiating projects, installing Drupal core, contributed modules and themes; to updating and managing them, Composer is recommended (but not required). Learn how to install Drupal 10 in cPanel 'public_html' folder using the new recommended template? As an aside, Drupal 10 is giving back power to site builders in many ways so they do not have to worry about Composer if they do not want to use it.