I recommend having the WP-CLI packages be regrouped under a common Composer type, like wp-cli-package.
In this way, you can provide a Composer plugin to define a custom installer for this type, which allows you to exert more control over the installation process (see Setting up and using custom installers ).
I recommend having the WP-CLI packages be regrouped under a common Composer type
Does this have to be something package authors remember to do, or is it something we can enforce?
This is done by the package authors, by adding the type key to their composer.json.
As an example, this is used for WordPress plugins, by setting "type" => "wordpress-plugin" in the plugin's composer.json. Together with https://github.com/composer/installers, this makes sure that plugins get installed into the wp-content/plugins folder instead of the vendor folder.
Cool. I think we need to do three things:
wp scaffold package includes the type.馃殺 馃殺
Most helpful comment
馃殺 馃殺