Expand description
Native reimplementations of the declarative Composer install plugins that
PHP projects (Magento / Mage-OS especially) depend on. This crate never runs
the PHP plugins or Composer scripts — it reproduces their declarative on-disk
effect natively. Every input lives in composer.json, which is what makes a
native port possible.
-
paths—composer/installers. A generic package-type→ install-path router (e.g.magento-theme→app/design/frontend/{$name}/,wordpress-plugin→wp-content/plugins/{$name}/), with rootextra.installer-pathsoverrides. Pure relocation; no copying. -
deploy—magento/magento-composer-installer. Amagento2-componentpackage (canonicallymagento/magento2-base) declares anextra.mapof[source, dest]pairs copied into the project root (this is howindex.php,pub/, theapp/etc/*skeleton land) plus anextra.chmodlist of permission masks. Also generatesapp/etc/vendor_path.php, which Magento’s bootstrap reads to locatevendor/. -
laravel— Laravel’spost-autoload-dumppackage discovery: writes thebootstrap/cache/packages.phpmanifest the framework would otherwise generate viaIlluminate\Foundation\ComposerScripts::postAutoloadDump.
Re-exports§
pub use deploy::ChmodEntry;pub use deploy::DeployPlan;pub use deploy::DeployStats;pub use deploy::VENDOR_PATH_PHP;pub use deploy::apply_deploy;pub use deploy::plan_deploy;pub use laravel::PACKAGES_CACHE;pub use laravel::STALE_CACHES;pub use laravel::blocking_post_autoload_dump;pub use laravel::build_package_manifest;pub use laravel::clear_compiled;pub use laravel::only_reproduced_scripts;pub use laravel::render_packages_php;pub use paths::InstallerPaths;pub use paths::install_path;pub use paths::install_path_relative_to_repo;pub use paths::unsupported_framework;