So there are one or two things to keep in mind: There should only be 1 vendor folder There should be a primary composer.json that’s in your project root, that would pull in all the dependencies You always check for and load the autoloader in the current directory, there’s no guarantee it is or isn’t … Read more
TL;DR If you want to support Composer, adding a composer.json is better then just let WPackagist create a package for you. There are several reasons, no one is really important, but considering that to create a composer.json does not require much effort, it probably worth it. composer.json Benefits Below a non-exhaustive list of benefits of … Read more
The answer is — you can’t because WordPress can’t. There is no dependency management concept in WP and it was the same case before Composer had even existed. The rise of autoload (Composer or otherwise) slightly helps with it, since you might just be getting different copy loaded (hopefully close enough) rather than outright fatal … Read more