You may need to run composer update with the "-no-plugins" option. The "zaporylie/composer-drupal-optimizations" plugin was skipped because it requires a Plugin API version ("^1.1") that does not match your Composer installation ("2.0.0"). The "hirak/prestissimo" plugin was skipped because it requires a Plugin API version ("^1.0.0") that does not match your Composer installation ("2.0.0"). The "acquia/blt-phpcs" plugin was skipped because it requires a Plugin API version ("^1.1") that does not match your Composer installation ("2.0.0"). The "oomphinc/composer-installers-extender" plugin was skipped because it requires a Plugin API version ("^1.0") that does not match your Composer installation ("2.0.0"). The "dealerdirect/phpcodesniffer-composer-installer" plugin was skipped because it requires a Plugin API version ("^1.0") that does not match your Composer installation ("2.0.0"). Here’s an example of what I saw initially on GovCon. Each project will have its own dependencies and each of those dependencies may (or may not) support Composer 2. This is the thing that is going to take a bit longer. Note that this also gives you the command to roll back to 1.x (which you may need). Use composer self-update -rollback to return to version 1.10.0 Updating Composer itself is super simple! Just run: composer self-update.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |