As per #2438, pm-download and pm-update are being deprecated in favour of composer.
It would be great to have a drush wrapper for composer. Any idea if this already exists somewhere? I imagine it would help bridge the gap of drupal and composer, especially for people who are less familiar with composer.
Here are some ideas:
- Command cm-update. Support for --security-only (maybe implemented via pm-updatestatus?), --check-updatedb, --entity-updates, --lock (implemented by composer require of exact version). Add support for "recommended version" checking, with detection when a newer recommended release is available (default composer require of ^a.b would ignore a newer major version).
- Command cm-install.
- Command cm-download alias cm-require.
- Command cm-remove. Checks modules have been uninstalled.
- Command cm-updatestatus = update --dry-run
- Automatic conversion from drupal to composer version numbers, can specify either.
- Brings power of drush aliases. Can run composer from any directory or even remotely. Can use alias groups.
- Brings power of drushrc, for example to turn on option --no-dev by default.
As per #2438, pm-download and pm-update are being deprecated in favour of composer.
It would be great to have a drush wrapper for composer. Any idea if this already exists somewhere? I imagine it would help bridge the gap of drupal and composer, especially for people who are less familiar with composer.
Here are some ideas: