composer++
summary
Shows how Composer is extended to solve five concrete pain points: unreliable script output, no background jobs, poor multi-module support, immutable composer.json sections, and lack of offline reinstall. Describes building a private-repo tools suite and a plugin that generates commands from a registry, using Symfony Process and Composer plugin hooks to run backgrounded tasks and control verbosity, swapping Composer’s JSON schema to allow nested extra data, and relying on Composer 2’s built-in offline and parallel-download features.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 2:00About Composer
- 5:10What Composer is
- 9:10Composer concept issues
- 10:37Composer terminology
- 13:51Composer internals
- 16:51Composer plugins
- 19:05Plugin types and examples
- 23:43Composer usage problems
- 27:01Offline mode and retries
- 29:13Background processes example
- 31:20Plugin problem solutions
- 33:38Environment variables issues
- 35:03Background process fix
- 36:28Composer 2.0 future
- 39:22Summary and recommendations
- 40:24Q&A
related talks
46mComposer Best Practices
01h 04mDemystifying Composer
48mPackage Design Principles in Practice
41mComposer and Drupal: Past, Present and Future
46mManaging dependencies is more than running "composer update"
40mBehind the Scenes of Maintaining an Open Source Project
50mTools of the Trade
01h 07mTaking Maximum Advantage of Drupal Core's Composer Template