The document discusses the integration of Composer in Magento 2 for PHP dependency management, detailing its role in handling packages through files like composer.json and composer.lock. It highlights the benefits of using Composer for installing and updating custom extensions while emphasizing the importance of semantic versioning. The text also provides practical guidance on setting up repositories and maintaining installed extensions effectively.

1. Magento 2
and
Composer

2. Peter Jaap
Blaakmeer
CTO elgentos
@PeterJaap
Ook; mede-organisator MUG050, vrijwilliger Meet Magento,
hobbybierbrouwer & bordspellenfanaat

3. What is composer?
Dependency management in PHP

4. Why would you use Composer?

5. What does this have to do with Magento 2?

6. composer.phar / composer.json / composer.lock

7. composer.phar
Binary used to work with composer

8. composer.json
require / require-dev / replace

9. composer.lock
Lockfile created when running composer update

10. Composer repositories
Packagist (default)
http://packages.magento.com/
http://packages.firegento.com/
Set up your own with Satis

11. Magento 2 Composer repository authentication
Why?
Keeping track of installed extensions
Keeping track of extensions purchased through Marketplace
Notifications of new versions!
Installing of patches!
How?
Through your magento.com account.

12. Custom extensions
Why?
Easy installable, updatable and reusable code.
How?
Place each extension in a separate Git repository
Add a composer.json that sets the name and dependencies
Add the Git repo link to the main composer.json file
Run composer update

13. Editing composer.json
(and run composer update)

14. Using composer.phar

15. Semantic versioning
- MAJOR.MINOR.PATCH
- works through Git tag
- tag every versioned release
- never use ‘dev-master’ or similar
- semver.org
1.0.2
>=1.0 <2.0
^1.2.3 (equal to >= 1.2.3 < 2.0.0, recommended)
Examples