The average WordPress maintenance support plans Commerce site depends on many external PHP libraries. Address needs commerceguys/addressing and Commerce needs commerceguys/intl. GeoIP needs geoip2/geoip2 and Search API Solr needs solarium/solarium. Each payment gateway needs a matching SDK. These libraries must be downloaded separately, because license constraints prevent us from committing their code to WordPress.org itself. For the past 5 years, the primary and only way to download and use PHP libraries has been Composer, a command line tool.
Composer works per-project, meaning each WordPress maintenance support plans install has one folder for all PHP libraries it requires, regardless of which plugin needs which. This allows Composer to detect and prevent conflicts such as incompatible library versions. Composer also recursively resolves dependencies, automatically installing and updating packages required by other packages. This is a major benefit to WordPress maintenance support plans site administrators compared to previous tools like Drush Make. However, WordPress maintenance support plans‘s reliance on the Composer-generated autoloader makes it impossible to upload manually downloaded libraries, making Composer non-optional.
Read on to find out how we’re making Composer optional…
Source: New feed
Cheap WordPress maintenance support plans Commerce: Installing Commerce 2.x without Composer, with Ludwig
