Alessandro Lai

I've did a quick check using [Composer require checker](https://github.com/maglnet/ComposerRequireChecker). This is the result, grepping for `common`: ``` $ composer-require-checker check composer.json | grep -i "common" | Doctrine\Common\DataFixtures\Loader | | |...

I did a small tryout of running tests without additional dev dependencies and that's really ugly.. The fixtures requires all the bundles, everything is an implicit / optional dependency... Argh!

Any news here? How can we help to push this forward?

This looks great, thank you @cebe! Can we help in any way? Is there a "TODO" list to complete this?

I think that option 1 (being context-aware when possible) could be a good solution, but the mantainer seems against that approach. Maybe we can pass the project's autoloader's file path...

Note: since Composer 2 (or since we use `jean85/pretty-package-versions` anyway), accessing `composer.json` info has low to no overhead, since we can retrieve information on installed packages from the Composer API,...

@cleptric what do you mean? We do... Do you have issues using it?

> @Jean85 We had a customer reach out and report similar issues as in https://github.com/getsentry/sentry-php/pull/1008. So you updated your package to work with Composer v1/v2 out of the box? We...

> @cleptric we could simply measure the overhead of ModulesIntegration just to play it safe and if it is really low, I say we enable it by default to unify...

What should `tracePropagationTargets` do? We can't do anything "automagically" in the base PHP SDK... Maybe it's feasible in the framework integrations, on the framework-provided clients.