delete_vendor_packages deletes needed composer files about strauss

[BrianHenryIE]

I suspect what's happening is that composer/composer is an explicit require dependency of one of your dependencies (a full composer.json would be helpful here) and so it is being copied and then deleted. An exclusion rule should be written for the Composer autoload files.

You could try setting the target_directory to vendor, and use the exclude_from_prefix setting for your two exclusions. Then it will prefix in-place and won't delete anything at all.

require_once __DIR__ . '/vendor/prefixed/autoload.php';

I think maybe that line won't be necessary after composer dump-autoload is run because you're using a sub-directory of vendor to copy the files to, and dump-autoload should scan the entire vendor directory

find vendor -type d -empty -delete

I've been meaning to add this to Strauss itself.

[TussendoorHQ]

Thanks for the astonishing fast reply Brian!

I searched for the requirement that had composer/composer in their requirements and funnily enough it was the strauss package itself! After switching to the .phar file the problem was resolved. I needed some extra changes too (also based on your reply). So for anybody coming accross this, these are my changes:

1. Removed brianhenryie/strauss from my requirements.
2. Now using the .phar from the latest release.
3. Changed the command in my prefixer.sh from vendor/bin/strauss to: php strauss.phar
4. Changed target_directory to: vendor
5. Renamed exclude_from_copy to exclude_from_prefix in my config to acommodate for the target_directory change.
6. Added the below to my autoload config as per issue 34 and this reply. (#34)

"classmap": [
    "vendor"
]

7. Also removed the autoload from the prefixed folder as this doesnt exist anymore. Only this line is now sufficient to autoload everything:

require_once __DIR__ . '/vendor/autoload.php';

The issue mentioned here is resolved. Still running into another issue where a specific directory (/lazy) of nesbot/carbon doesnt get prefixed. But I will create a new issue for it as it is not related.