Skip to content

Shipping unprefixed dependencies causes conflicts. #5916

@ju1ius

Description

@ju1ius

Bug Report

The wp-cli phar release currently ships with unprefixed composer dependencies.

Since most wp-cli commands need to load the wordpress application, this can cause conflicts in case a plugin or the application/website itself require the same dependency with different version constraints.

For example:

  • an application or plugin requires psr/log:^3.0, but wp-cli ships with psr/log:^2.0
  • a command in an application or plugin requires symfony/console:^7.0, but wp-cli ships with symfony/console:^3.4
  • and so on...

An external tool should not impose a specific version of a dependency on the application developper.

In order to get rid of these issues, wp-cli should do what phpunit does in its phar release: ship all dependencies under a common vendor prefix (using i.e. humbug/php-scoper).

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions