Théo FIDRY

Hi, at the moment I don't think so. Maybe it would be possible by adding an environment variable before executing the installation?

Coming back to this: is there any reason for this? Because such a library would not be any different from another. It just comes from a different directory but it's...

>PHPStan looks around its vendor directory to see the dependencies used in the analysed project Is it a behaviour specific to when PHPStan is installed as a package instead of...

would providing an environment variable be enough here?

Erratum actually that would not work since what you want is to check afterwards. I think in 99.99% of the cases, you can check for the path (`root/vendor-bin/namespaceName/{vendor, composer.json, composer.lock}`)....

I am really not sure how do you expect the plugin to fix this? By doing `composer install --no-dev`, since you installed it as a dev dependency, you are removing...

Hi! Glad to find this issue as I was about to open one about it :) Disclaimer: I'm the current maintainer of https://github.com/bamarni/composer-bin-plugin. First of all, for clarification an introduction...

>Is there a special reason to limit the depth ? Yes! The reason is that it represents environments: https://github.com/theofidry/AliceBundle/blob/master/doc/advanced-usage.md#environment-specific-fixtures I am not sure how this could be made either better/less...

To be honest I'm not sure if it's because it was desired or to keep BC. I'm happy to change this but this requires some checking and probably a new...

This is a bit annoying indeed...