3

There is no problem with installing Composer globally, but there may be a problem with using composer global require to install individual Composer-managed projects globally. You should not run in to this trouble just using Composer on the server to composer install your various Drupal 8 and Drupal 9 sites, but you should be aware of the potential for ...


2

The most common way to 'flip' a project from not having Composer managed dependencies to being managed by Composer is to use the Composerize project: https://github.com/grasmash/composerize-drupal


1

I wouldn't say there is a most common way. Drupal is by default now composer ready since it introduced two project templates of its own. The answer depends on the specific requirements. If you want to switch between different composer templates it's also no problem to start a new composer project, require the packages of the installed modules and then move ...


1

The reason this doesn't work because the "stable preference" of composer is not a preference but a hard choice which you can not override with anything except specifying an exact version. If you have "prefer-stable": true, in your composer.json then the only way to install a beta module is composer require 'drupal/bricks:2.0.2-beta2'. ...


Only top voted, non community-wiki answers of a minimum length are eligible