Optimize the autoloader when running Composer commands

This looks good. Is there way we actually confirm this gives a performance boost. Running kernels tests that do run composer seem to take the same amount of time.

The performance post depends completely on the application. It should be much faster for applications that have large number of dependencies, because optimizing the auto loader reduces disk reads during autoloading.

This is the best practice recommended by composer itself for production applications. Also, don’t think there’s any downside to it. The only time that you should not optimize the auto loader is when you are working in a development environment, because the dynamic file discovery makes it easier during development to create new files, change names, etc., without having to dump the auto loader each time you make a change.

See https://getcomposer.org/doc/articles/autoloader-optimization.md#:~:text=....

I agree with @grasmash here. There is no obvious downside to doing this. I think we should go for it - it's an easy, unobtrusive fix.

Merged into 3.0.x and cherry-picked to 3.1.x. Thanks!

Automatically closed - issue fixed for 2 weeks with no activity.