Introduction to Composer
We use Composer to manage components and their dependencies. Using Composer to get the Adobe Commerce and Magento Open Source software metapackage provides the following advantages:
- Reuse third-party libraries without bundling them with source code
- Reduce extension conflicts and compatibility issues by using a component-based architecture with robust dependency management
- Adhere to PHP-Framework Interoperability Group (FIG) standards
- Repackage the software with other components
- Use the software in a production environment
You can also download an archive file for a specific version of Adobe Commerce or Magento Open Source in either ZIP or TAR format. Installing the software from an archive lacks the advantages of using Composer. Contributing developers should use the git-based installation method.
Links to code
The key to developing any component is its composer.json
file, which specifies version and dependency information for a component, among other things. You can look at the code, such as:
- Metapackage, look at
<magento_root>/composer.json
. - Customer module
- Luma theme
- en_us language package
For more information
For more information about Composer, see the Composer documentation.