Composer Best Practices
summary
Composer advice focuses on actionable rules: commit composer.lock so installs are reproducible and fast; tag releases before breaking and maintain a changelog; prefer use the caret (^) for libraries so minor/patch updates stay safe while allowing fixes; add packages with composer require rather than hand-editing composer.json; resolve conflicts by tightening bad wildcards or asking maintainers to relax them; require a forked branch via a VCS repository + alias so other deps still resolve; use composer scripts to run vendor/bin tools like phpunit.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 0:13About me
- 1:32Composer
- 1:51Semantic Versioning
- 4:42Who View
- 5:39Release Packages
- 7:41Tagging
- 9:55Review
- 10:29Help
- 11:10Constraint
- 11:21wildcard ranges
- 12:44orange
- 17:45carrot
- 20:01update
- 21:18stabilities
- 21:39stable tags
- 22:12branch
- 31:10log file
- 31:57faster installs
- 32:26reproducible installs
- 33:17commit
- 34:40custom commands
- 35:09test commands
- 36:37final tip
- 38:42Turn Proxy
- 39:18Fast Reliable
- 39:43Private Packages
- 40:47Open Source
