Bundle / prefix dependencies to avoid conflicts with other plugins

[borekb]

We depend on packages like phpmyadmin/sql-parser or symfony/process, which we manage by Composer.

The problem is that if other plugins use this approach as well (which is increasingly likely, especially for the more complex ones), there might be version conflicts. For example, if VersionPress depends some-library at version 1.0 and another plugin at version 2.0, there will very likely be hard to debug errors for the user.

We've known about this problem for a while, see #188, but maybe we should revisit it as in the meantime, some possible solutions popped up:

• Imposter
• Mozart (both are actually )
• PHP-Scoper

Another approach might be to bundle everything to a single file, similarly to webpack, but I'm not sure anything like that exists for PHP or that WordPress plugin reviewers would be too happy about it :)

The tools above would need to be tested, they are probably quite fragile by nature.

Some more resources about this:

• Composer issue: Dependency Hell in Composer composer/composer#2609
• How to prevent Composer dependency conflicts amongst WP plugins? - WordPress Development Stack Exchange
• What are the workarounds when Composer dependencies conflict in versions? - Stack Overflow

[borekb]

Delicious Brains recently blogged about this: PHP Scoper: How to Avoid Namespace Issues in your Composer Dependencies.