Composer dependencies
What to consider when adding a Composer dependency:
- It's serving a goal worthy of adding a dependency OR we're refactoring an existing dependency out of core.
- It isn't huge (e.g. the dependency isn't increasing our distro size by 30%).
- Its dependencies, if any, don't land us in spider web of further dependencies or require something our app servers cannot provide. They have been audited and are modest & reasonable.
- We have reasonable certainty the dependency will continue to be maintained for 5+ years into the future.
- The dependency is to serve code in the core repo, not an addon elsewhere.
We take dependencies very seriously; do not add them frivolously.
0