Composer Best Practices 2018
summary
Packages.org hosts ~200,000 packages and 1.2M versions and Composer sees ~22 releases since Jan 2017 with ~900 issues closed and ~300 PRs. Always commit the lock file so deployments run deterministic composer install --prefer-dist instead of updating. Build artifacts on CI, reuse the Composer cache, run composer dump-autoload -o or classmap-authoritative for production, test libraries with composer update --prefer-lowest --prefer-stable, resolve lockfile merges by checking out the base branch lock file and rerunning composer update, and verify platforms with composer check-platform-reqs.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 2:56Composer best practices
- 7:01Deployments
- 12:12Deploy without the lock file
- 12:52Dependencies
- 16:05Autoloader
- 17:30Classman
- 19:04Changes in Composer
- 20:46Interoperability
- 22:09New Features
- 24:22With All Dependencies
- 26:45CI Testing for Libraries
- 29:32Semantic Versioning
- 32:25Application Versioning
- 33:31Updates
- 37:13Oh Sorry
- 37:30Platform Requirements
- 39:24Platform Configuration
- 41:54Composer Plugins
- 44:33Summary
