peertopark/composer-bower-bridge

Bower integration for Composer packages.

1.0.0 2017-01-25 23:05 UTC

Requires

• php: >=5.3
• composer-plugin-api: ^1
• eloquent/composer-npm-bridge: ^3.0

Requires (Dev)

• composer/composer: dev-master
• eloquent/phony: ^0.8
• icecave/archer: dev-develop
• phpunit/phpunit: ^4

MIT

• hespert

• package
• plugin
• composer
• Bridge
• integration
• bower
• composer-plugin

README

Bower integration for Composer packages. Based on the on (and shamelessly stolen from) [eloquent/composer-npm-bridge] [eloquent/composer-npm-bridge]: https://packagist.org/packages/eloquent/composer-npm-bridge

Installation

• Available as Composer package peertopark/composer-bower-bridge.

Requirements

• The npm executable must be available in PATH.

Usage

To utilize the Composer NPM bridge, simply add eloquent/composer-npm-bridge to the require section of the project's Composer configuration:

composer require eloquent/composer-npm-bridge:^3

NPM dependencies are specified via a package.json configuration file in the root directory of the Composer package. Source control should be configured to ignore NPM's node_modules directory, similar to Composer's vendor directory.

How does it work?

The Composer NPM bridge is a Composer plugin that automatically installs and updates NPM packages whenever the corresponding Composer command is executed. To detect compatible packages, the bridge inspects Composer package configuration information to find packages that directly require the eloquent/composer-npm-bridge Composer package itself.

In addition to normal operation, composer install will install NPM dependencies for all Composer packages using the bridge. This includes the root package, as well as Composer dependencies. Similarly, composer update will install NPM dependencies for all Composer dependencies using the bridge. It will also update and shrinkwrap the NPM dependencies for the root project.

NPM dependencies will be installed exactly as if npm install were run from the root directory of the package. This applies even if the package is installed as a dependency.

Caveats

Because NPM dependencies are installed underneath the root directory of the Composer package, Composer may complain about working copy changes when the package is installed as a dependency. Source control should be configured to ignore the node_modules directory in order to avoid this.