composer/installers
Custom installer paths for Composer. Maps package types (e.g., WordPress plugins/themes, Drupal, Joomla) to appropriate directories so dependencies land where your CMS expects them, with flexible installer definitions for multi-project setups.
Full Changelog: https://github.com/composer/installers/compare/v2.2.0...v2.3.0
Full Changelog: https://github.com/composer/installers/compare/v2.1.1...v2.2.0
Full Changelog: https://github.com/composer/installers/compare/v2.1.0...v2.1.1
tastyigniter-module type to TastyIgniter (#503)extra.plugin-modifies-install-path to composer/installers for Composer 2.3 support, see docs if you are writing your own custom installer plugin.As of Composer 2.1, the Composer\InstalledVersions class has a
getInstalledPackagesByType
method which can let you figure out at runtime which plugins/modules/extensions are installed.
It is highly recommended to use that instead of building new custom installers if you are building a new application. This has the advantage of leaving all vendor code in the vendor directory, and not requiring custom installer code.
customcertelement for Moodle, #408.target-dir from package attributes, #432.Happy New Year! 🎅🏻
core to concrete5 installer.How can I help you explore Laravel packages today?