Christophe Coevoet

> Why not? My code can access classes from tools if they are in normal require-dev directly. That's the whole point. `require-dev` brings classes in your main autoloader. `require-tools` would...

@mxr576 scoping a phar with php-scoper requires that project maintainers do it, to configure which classes can be scoped and which one must not be renamed because they are necessary...

Also, what you are asking for is not a DI container (which supposes that your class still uses DI and so the constructor stays the same than today). It is...

> * Create a custom `Policy` implementation, aware of the local packages that will make the Solver accept `dev-local` for them, no matter the actual requirement This is not something...

This caused issues in the past, when the temp directory and the vendor directory are not on the same drive, when attempting to move the directory. > Unrelated, but I...

We cannot extract directly in the right location. For instance, the zip archive generated by GitHub (which are the majority of zips downloaded by composer, as the majority of packages...

Be careful when using symlinks: this will change the relative location of the source code compare to the vendor folder, which will break cases where the code does things like...

That trick still requires knowing the name of the root folder, which is currently discovered by composer *after* unzipping.

> A global install on npm also means you could use it locally though, doesn't it? @alcohol not by default. You need an additional env variable to tell Node to...

I think this is indeed a mistake added in https://github.com/composer/composer/commit/1a725d5e1f7d24aeab9355b2174681b7927346dd#diff-ff2fcaab03a71a9baa1c17c54722d382e64665c099076391965ecfa35ec4b8edR35 where it adds `$path` as the CWD for executing the command, while it was not the case before, and so...