Download the PHP package dex/composer-plug-and-play without Composer
On this page you can find all versions of the php package dex/composer-plug-and-play. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Informations about the package composer-plug-and-play
Composer Plug and Play
Adds to Composer, PHP's dependency manager, the ability to plug and play packages without necessarily installing
a new dependency on composer.json
.
Installation
Composer Plug and Play requires Composer
2.3.0
or newer.
Global installation
You can install Composer Plug and Play globally to use its abilities in all your local projects.
Usage
Initialize a plug and play structure:
Create or clone a Composer package into packages/<vendor>/<package>
folder and run:
Additional configuration
You can add some additional configuration in packages/composer.json
to add more data in the final resolution of the
composer.json
file.
Commands
All commands use the plug-and-play.json
and plug-and-play.lock
files as source to project dependencies instead of
composer.json
and composer.lock
original files.
You can use composer pp
and composer pp:*
as alias for all commands.
plug-and-play
: installs plug and play dependencies together project dependencies.plug-and-play:add
: require a package intopackages/composer.json
.plug-and-play:dump
: same thatcomposer dump-autoload
, but usingplug-and-play
files.plug-and-play:init
: initialize plug and play plugin.plug-and-play:install
: same thatcomposer install
, but usingplug-and-play
files.plug-and-play:reset
: removeplug-and-play
files.plug-and-play:run
: same thatcomposer run-script
, but usingplug-and-play
files.plug-and-play:update
: same thatcomposer update
, but usingplug-and-play
files.
Directories and files
Composer Plug and Play plugin needs a packages
folder in
the project root directory where the plug and play structure will live.
The plug-and-play.json
and plug-and-play.lock
files will contain the real project dependencies and plug and play
dependencies.
Your project directory will look like this:
Ignore plugged packages
Sometimes you may need to ignore a package that is under development, for that adds in packages/composer.json
something like this and run composer plug-and-play
.
Require dev dependencies from plugged packages
When developing some package or library you may need to require its dev dependencies, for that adds in
packages/composer.json
something like this and run composer plug-and-play
that the require-dev
dependencies will
be installed.
Autoload (strategy)
You may have some problems with symlinks and recursion when developing packages inside another application or package,
for that, you can use experimental:autoload
strategy.
This strategy will create a simple copy of your composer.json
in packages/vendor
directory to do a symlink from your
original vendor
directory.
To activate it, you should change your packages/composer.json
.
You must add to autoload-dev
the packages that you want to map its autoload and add to require-dev
the packages
that you want to require its dev dependencies.
License
Composer Plug and Play is licensed under the MIT license. See the license file for more details.
All versions of composer-plug-and-play with dependencies
ext-json Version *
composer-plugin-api Version ^2.0