copy third-party libs instead of using Composer autoloader (#256) #260

stklcode · 2023-03-31T18:54:38Z

fixes #256

The autoloader mechanism is quite heavy for a single dependency and requires composer and vendor dir to be part of the final product.

We yet have generated/minified resources in our project, so this is the minimalistic approach to copy the CrawlerDetect lib, too and extend the custom autoloader mechanism.

This is not a pretty solution, but the project is not really Composer compatible. (no PSR-4 namespaces, requirement for minified files that are generated from dev-dependencies, etc.).

This way we ca postpone the decision to heavily rework the project structures while having a runnable artifact again.

The autoloader mechanism is quite heavy for a single dependency and requires composer and vendor dir to be part of the final product. We yet have generated/minified resources in our project, so this is the minimalistic approach to copy the CrawlerDetect lib, too and extend the custom autoloader mechanism.

florianbrinkmann · 2023-09-17T14:38:09Z

The only thing missing here would be to add the CrawlerDetect file(s) to the lib folder, right?

The autoloader mechanism is quite heavy for a single dependency and requires composer and vendor dir to be part of the final product. We yet have generated/minified resources in our project, so this is the minimalistic approach to copy the CrawlerDetect lib, too and extend the custom autoloader mechanism.

stklcode · 2023-09-17T16:14:21Z

You're right, seems the line got lost at some point. Re-added the missing directory to the copy-file list in composer.json, so it's populated after composer install

florianbrinkmann

LGTM!

The autoloader mechanism is quite heavy for a single dependency and requires composer and vendor dir to be part of the final product. We yet have generated/minified resources in our project, so this is the minimalistic approach to copy the CrawlerDetect lib, too and extend the custom autoloader mechanism.