How to install require-dev dependencies together with composer require package-name?
#11451
-
|
I need to install packages from the list of But it installs only packages, listed in the And I can't find any key to enable this in the documentation. So, is there any way to automate installing of |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 6 replies
-
|
Do you have COMPOSER_NO_DEV env var set? Otherwise by default it should always install require-dev. Oh or maybe it's a misunderstanding.. Composer installs your project's require-dev always, but never your dependencies require-dev section, as those are only useful when developing the package in question, not when using the package as a dependency. That's the whole point of splitting things up in require-dev. |
Beta Was this translation helpful? Give feedback.
-
I need exactly this, to run unit tests in a dependent project. They can't be run via simply installing the dependent project separately, because it requires the framework core files. Here is my project: https://git.drupalcode.org/project/opentelemetry and it requires Yes, I can do it manually like this: But it'll be much better to have something like this: |
Beta Was this translation helpful? Give feedback.
-
|
In Drupal.org pipeline it's seems workarounded via manually parsing the Here is the code that does this: https://git.drupalcode.org/project/drupalci_testbot/-/blob/dev/src/DrupalCI/Plugin/BuildTask/BuildStep/CodebaseAssemble/ComposerContrib.php#L100-105 |
Beta Was this translation helpful? Give feedback.
-
|
Yeah I guess this is a side-effect of Drupal's historical baggage and the fact that (AFAIK) it cannot easily run from the vendor dir, so you need to install your project inside a drupal project to be able to test it, etc.. More modern projects typically do not have this limitation and then everything works more easily. Anyway there is no way we can allow this IMO as it would lead to way too many conflicts. |
Beta Was this translation helpful? Give feedback.
-
|
How can adding an additional option lead to conflicts for those not using the new option? 🤔 |
Beta Was this translation helpful? Give feedback.
-
|
@kopeboy it is not about those not using the option. It is about being unusable for people using that option. including dev requirements of all dependents in the dependency resolution means Composer has to find a set of dependencies compatible with all those dev requirements of all packages at once. The chance of finding such a solution without dependency conflicts is very low. This description would be a direct ticket for the dependency hell. |
Beta Was this translation helpful? Give feedback.
-
|
I don't think this is a just a Drupal issue. |
Beta Was this translation helpful? Give feedback.
-
|
@joachim-n No sure, but with that set up you can easily go in the path repo's dir, and run composer install to run tests in there etc. |
Beta Was this translation helpful? Give feedback.
Yeah I guess this is a side-effect of Drupal's historical baggage and the fact that (AFAIK) it cannot easily run from the vendor dir, so you need to install your project inside a drupal project to be able to test it, etc.. More modern projects typically do not have this limitation and then everything works more easily.
Anyway there is no way we can allow this IMO as it would lead to way too many conflicts.