Run Any Composer Package Instantly with CPX – The PHP npx Alternative

Overview

In modern PHP development Composer is the de‑facto package manager, but developers often need temporary tools without polluting project dependencies, avoid global version conflicts, or run a package command quickly.

Only need a tool temporarily, without global install or dependency pollution.

Different projects require different tool versions; global Composer installs cause conflicts.

Want to execute a package command instantly without manual require or autoload configuration.

CPX (Composer Package Executor) was created to address these pain points. It works like Node.js’s npx, allowing “run‑once” execution of any Composer package command.

Composer

Composer is PHP’s dependency management tool. Its core functions include managing project dependencies (require, update, remove), generating autoload files supporting PSR‑4/PSR‑0, and supporting script hooks and plugin extensions.

Manage project dependencies (require, update, remove, etc.).

Automatically generate autoload files, supporting PSR‑4/PSR‑0.

Support script hooks, plugin extensions, and other advanced features.

Common commands:

composer require monolog/monolog
composer update
composer dump-autoload

Composer also supports global installation of tools:

composer global require friendsofphp/php-cs-fixer

Drawbacks of global installation:

Dependency conflicts (e.g., incompatible Symfony Console versions).

Only one version can exist, making switches cumbersome.

Upgrading or uninstalling global packages is inconvenient.

CPX: Composer Executor

CPX (cpx/cpx) aims to let you run any Composer package command on the fly, just like npx, without global installation and without polluting project dependencies.

1. Install CPX

Recommended installation via Composer global:

composer global require cpx/cpx

2. Basic Usage

CPX command format: cpx <package> <command> [options] Example – temporarily format code with PHP‑CS‑Fixer: cpx friendsofphp/php-cs-fixer fix ./src If the package provides a single command or the command name matches the package name, the command can be omitted: cpx friendsofphp/php-cs-fixer fix ./src CPX automatically downloads and caches the package in an isolated directory, reusing it on subsequent runs without re‑download.

3. Built‑in Commands

CPX includes standard commands that automatically adapt to common tools: cpx check: static analysis (PHPStan, Psalm). cpx format or cpx fmt: code formatting (PHP‑CS‑Fixer, Pint). cpx test: test frameworks (PHPUnit, Pest).

Examples:

cpx check
cpx format --dry-run
cpx test

4. Additional Useful Commands

cpx aliases

: view aliases for common packages (e.g., cpx php-cs-fixer). cpx list: list previously used packages. cpx update: update a package to the latest version. cpx clean: clean rarely used package caches. cpx exec <file.php>: run a PHP file with Composer autoload. cpx exec -r '<php code>': execute raw PHP code directly. cpx tinker: start an interactive REPL.

5. Typical Scenarios

Temporary formatting, analysis, or testing without installing tools globally.

Multiple projects can use different versions of the same tool without interference.

One‑off packages avoid dependency pollution and manual cleanup.

Advantages and Implementation

Isolation : each package is cached separately, preventing dependency clashes.

Efficient reuse : repeated runs of the same package skip re‑download.

Auto‑adaptation : check/format/test commands automatically detect tools already installed in the project.

Zero dependencies : CPX itself has no external dependencies, keeping it lightweight and secure.

Extensible : supports aliases, REPL, exec and other advanced usages.

CPX works by maintaining an independent cache directory under the user’s home, downloading packages on demand, and automatically handling autoload and dependency isolation.

Best‑Practice Recommendations

Use CPX for everyday development, CI/CD pipelines, and ad‑hoc scripts.

Keep long‑term library dependencies in composer.json.

When facing dependency conflicts or version switching, consider CPX first.

Conclusion

Composer solves PHP dependency management, while CPX makes “run‑once” package execution possible, greatly improving flexibility and efficiency for individual developers and teams alike.

For more details, refer to the official CPX documentation.