A Composer plugin that manages NPM and Bower dependencies directly within PHP projects without requiring Node.js.
Fxp Composer Asset Plugin is a Composer plugin that allows PHP developers to manage NPM and Bower dependencies directly within their `composer.json` files. It solves the problem of needing separate Node.js tooling by translating asset package metadata into a format Composer can understand, streamlining dependency management for PHP projects.
PHP developers working on projects that require frontend libraries (like JavaScript or CSS frameworks) and want to manage all dependencies through Composer without installing Node.js or Bower separately.
Developers choose this plugin to unify dependency management under Composer, reducing toolchain complexity and avoiding the need to maintain multiple package managers. It integrates seamlessly with existing Composer workflows while supporting both public and private asset registries.
NPM/Bower Dependency Manager for Composer
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Translates NPM and Bower packages into Composer format, allowing PHP projects to manage all dependencies through a single tool, reducing toolchain complexity as described in the README.
Integrates with public and private NPM/Bower registries, plus VCS repositories like Git and GitHub, enabling flexible asset sourcing without separate Node.js setup.
Includes lazy loading of package definitions and import filters to speed up updates, which is particularly useful for large projects with many assets, as highlighted in the features.
Fully compatible with Composer commands like require, remove, and show, making it easy to adopt in existing PHP workflows without learning new tools.
The README explicitly states that the plugin is no longer actively developed, with the maintainer shifting to Foxy, an incompatible successor, meaning no new features or updates.
Only handles asset dependency management, not modern frontend tasks like bundling or minification, requiring additional tools for full asset pipelines.
Setup can be intricate, with need for custom VCS repository configs and potential issues with version range conversions, as noted in the documentation sections.