I've got a question regarding drupal/core and drupal/core-recommended. So drupal/core-recommended uses fixed versions of the packages, which the corresponding core version was tested with. And yes it does make sense that this prevents bugs introduced by version differences of let's say different versions of symfony packages for example.

But on the other hand, let's say you install a dev version of a modul or any other third party library with composer, which explicitly needs a different version of a symfony component than drupal/core-recommended, these locked versions of the core dependencies will cause trouble, as the third party library/the module could not get installed due to version conflicts.

So how would one deal with this kind of situation when using drupal/core-recommended?

I've got a question regarding drupal/core and drupal/core-recommended. So drupal/core-recommended uses fixed versions of the packages, which the corresponding core version was tested with. And yes it does make sense that this prevents bugs introduced by version differences of let's say different versions of Symfony packages for example.

But on the other hand, let's say you install a dev version of a module or any other third-party library with composer, which explicitly needs a different version of a Symfony component than drupal/core-recommended, these locked versions of the core dependencies will cause trouble, as the third party library/the module could not get installed due to version conflicts.

So how would one deal with this kind of situation when using drupal/core-recommended?