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.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package composer-plug-and-play

Composer Plug and Play

Packagist Version PHP Version Downloads License Tests

Composer Plug and Play lets you develop local packages inside a project without modifying composer.json. Keep your working packages in packages/, run composer plug-and-play, and get a fully resolved Composer environment — without polluting your real lock file.

Table of Contents

Why?

Working with local packages via path repositories in composer.json pollutes the project's composer.json and composer.lock with development-only entries that must not be committed.

Composer Plug and Play keeps this configuration isolated in packages/composer.json and packages/plug-and-play.lock, so your real composer.json stays clean.

Requirements

Installation

Global installation

You can install Composer Plug and Play globally to use its abilities in all your local projects.

Quick Start

  1. Initialize the plug-and-play structure in your project:

  2. Clone or create a package inside packages/:

  3. Run plug-and-play to resolve everything:

Your package is now available as if installed via Composer, without touching composer.json.

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.

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.

Command Description
plug-and-play Installs plug and play dependencies together with project dependencies
plug-and-play:add Require a package into packages/composer.json
plug-and-play:dump Same as composer dump-autoload, but using plug-and-play files
plug-and-play:init Initialize plug and play plugin
plug-and-play:install Same as composer install, but using plug-and-play files
plug-and-play:reset Remove plug-and-play files
plug-and-play:run Same as composer run-script, but using plug-and-play files
plug-and-play:update Same as composer update, but using plug-and-play files

Configuration

You can add additional configuration in packages/composer.json under the extra.composer-plug-and-play key.

Ignore plugged packages

Sometimes you may need to ignore a package that is under development:

Require dev dependencies from plugged packages

When developing a package or library you may need to require its dev dependencies:

Autoload dev dependencies from plugged packages

When developing a package or library you may need to autoload its dev dependencies:

Contributing

Contributions are welcome. Please open an issue before submitting a pull request so the change can be discussed first.

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

PHP Build Version
Package Version
Requires php Version ^8.3
ext-json Version *
composer-plugin-api Version ^2.3
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package dex/composer-plug-and-play contains the following files

Loading the files please wait ...