Composer is used to list PHP dependencies as well as external assets.
A few packages are used to expand composer's functionality:
- cweagans/composer-patches: applies custom patches to dependencies
- wikimedia/composer-merge-plugin: merges additional composer.json files
- composer/installers: supports additional types of packages and their custom paths
- mnsami/composer-custom-directory-installer: allows custom paths for any type of package
- derhasi/composer-preserve-paths: to force paths and files to be preserved
The dependences and managed and organized into different directories:
- app: WordPress core, plugins and themes
- assets: External JavaScript, CSS and other kinds of assets
- vendor: Composer packages and remaining dependencies
Composer will look for composer.json configuration files in a variety of places.
The main file is loaded with the minimum set of configuration and dependencies:
- composer.json
The composer/ directory contains files that add additional dependencies as
WordPress Contributed plugins and themes, as well as external assets.
These are not by default read by composer and must be copied to the composer
directory for inclusion in the project deployment.
The composer/ directory may contain files to add additional dependencies.
Composer will look for files under these paths:
- composer/composer.json
- composer/*/composer.json
- composer///composer.json
- composer///*/composer.json
Custom configuration and dependencies may be loaded from:
- composer/composer.local.json
The Core configuration is loaded to provide additional dependencies:
- app/core/composer.json