Replies: 1 comment 3 replies
-
|
Beta Was this translation helpful? Give feedback.
-
|
--no-dev would not help, as we always must resolve all dependencies together. --no-dev only applies to the install step, it does not change the dependency resolution. So I don't think this can be done at all, I'm not sure what this magical --strict flag would be supposed to do but I doubt we can fix this situation. |
Beta Was this translation helpful? Give feedback.
-
I just want to be sure that I, as a vendor, specific the right minimum version. Because my "customers" dont install my dev packages, this will maybe cause errors in their packages. Maybe "strict" is not the word for this use case. I guess it is more of a validation |
Beta Was this translation helpful? Give feedback.
-
|
Yeah I understand what you are trying to do, and it makes sense, but it's not doable unless you make sure dev dependencies do not conflict with non-dev ones. If you want to be safe then make sure to put in require whatever version --prefer-lowest resolves to based on all requirements. That way no surprises for users of the package. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I tested
--prefer-lowestaccording to the offical docs.Because some of my test tools requires a specific version of a framework, I found the following use case:
My Setup
composer.json
Problem
The
package/test-corecan only check the same version ofpackage/core. So still, with--prefer-lowestwe install at least version above 9.20 in our (unit) tests.This example is really simplified. In my use case, there are different versions with different requirements for the test package
Possible Solution
Add a "strict" mode when installed with
--prefer-lowestwith the dev packages. This would be the best scenario, but it would probably break some already defined CI pipelines.Another
--strictargument would probably solve this too :)Beta Was this translation helpful? Give feedback.
All reactions