PHPackages                             laradic/composer-merge-plugin - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. laradic/composer-merge-plugin

ActiveComposer-plugin[Utility & Helpers](/categories/utility)

laradic/composer-merge-plugin
=============================

Composer plugin to merge multiple composer.json files

2.0.4(5y ago)0812MITPHPPHP >=5.3.2CI failing

Since Aug 23Pushed 5y ago1 watchersCompare

[ Source](https://github.com/laradic/composer-merge-plugin)[ Packagist](https://packagist.org/packages/laradic/composer-merge-plugin)[ RSS](/packages/laradic-composer-merge-plugin/feed)WikiDiscussions master Synced 2w ago

READMEChangelogDependencies (5)Versions (13)Used By (0)

laradic/composer-merge-plugin
=============================

[](#laradiccomposer-merge-plugin)

This is a fork of `wikimedia/composer-merge-plugin`. It adds all merged composer files their library name to the root composer its `replace` configuration during install/update. This way if you have the library in both your root composer's `require` but also have it locally merged with merge plugin, the `require` dependency is ignored and as such the library wont be installed to the vendor.

### Changes

[](#changes)

##### 1.0.0

[](#100)

```
// MergePlugin.php
protected function addPackageToRootReplaces(ExtraPackage $package)
{
$root = $this->composer->getPackage();
$rootReplaces = $root->getReplaces();
$constraint =  new EmptyConstraint();
$constraint->setPrettyString('*');
$rootReplaces[] = new Link($root->getName(), $package->getPackage()->getName(),$constraint,'replaces','*');
$root->setReplaces($rootReplaces);
$this->logger->info("Added package {$package->getPackage()->getName()} to root composer replace");
}
```

##### 1.1.0

[](#110)

In order to customize the `replaces` you should now:

```
{
    "extra": {
        "merge-plugin": {
            "include": ["addons/*/*/*/composer.json", "core/*/*/composer.json", "packages/*/*/composer.json"],
            "replaces": ["addons/*/*/*/composer.json", "packages/*/*/composer.json"],
            "recurse": true,
            "replace": false,
            "merge-dev": true
        }
    }
}
```

Composer Merge Plugin
=====================

[](#composer-merge-plugin)

[![Latest Stable Version](https://camo.githubusercontent.com/07ba86bc47e9e5d84772325331a364951d4a588406993832ca152f579c21d46e/68747470733a2f2f696d672e736869656c64732e696f2f7061636b61676973742f762f77696b696d656469612f636f6d706f7365722d6d657267652d706c7567696e2e7376673f7374796c653d666c6174)](https://packagist.org/packages/wikimedia/composer-merge-plugin) [![License](https://camo.githubusercontent.com/cece6304369a520046e8a078fa680ea49e21cba4a073b00b42e9e543ea119570/68747470733a2f2f696d672e736869656c64732e696f2f7061636b61676973742f6c2f77696b696d656469612f636f6d706f7365722d6d657267652d706c7567696e2e7376673f7374796c653d666c6174)](https://github.com/wikimedia/composer-merge-plugin/blob/master/LICENSE)[![Build Status](https://camo.githubusercontent.com/3e750d5c928334624bc8a6d8e6775aac7b29e2b5db3d4e7270ac9b94896169fd/68747470733a2f2f696d672e736869656c64732e696f2f7472617669732f77696b696d656469612f636f6d706f7365722d6d657267652d706c7567696e2e7376673f7374796c653d666c6174)](https://travis-ci.org/wikimedia/composer-merge-plugin)[![Code Coverage](https://camo.githubusercontent.com/ebf3854e9a514c51f3c6eadc05f9720425e84b0910679def07e8acffc35f1dc4/68747470733a2f2f696d672e736869656c64732e696f2f7363727574696e697a65722f636f7665726167652f672f77696b696d656469612f636f6d706f7365722d6d657267652d706c7567696e2f6d61737465722e7376673f7374796c653d666c6174)](https://scrutinizer-ci.com/g/wikimedia/composer-merge-plugin/?branch=master)

Merge multiple composer.json files at [Composer](https://getcomposer.org/) runtime.

Composer Merge Plugin is intended to allow easier dependency management for applications which ship a composer.json file and expect some deployments to install additional Composer managed libraries. It does this by allowing the application's top level `composer.json` file to provide a list of optional additional configuration files. When Composer is run it will parse these files and merge their configuration settings into the base configuration. This combined configuration will then be used when downloading additional libraries and generating the autoloader.

Composer Merge Plugin was created to help with installation of [MediaWiki](https://www.mediawiki.org/wiki/MediaWiki)which has core library requirements as well as optional libraries and extensions which may be managed via Composer.

Installation
------------

[](#installation)

Composer Merge Plugin requires [Composer 1.0.0](https://getcomposer.org/) or newer.

```
$ composer require wikimedia/composer-merge-plugin

```

Usage
-----

[](#usage)

```
{
    "require": {
        "wikimedia/composer-merge-plugin": "dev-master"
    },
    "extra": {
        "merge-plugin": {
            "include": [
                "composer.local.json",
                "extensions/*/composer.json"
            ],
            "require": [
                "submodule/composer.json"
            ],
            "recurse": true,
            "replace": false,
            "ignore-duplicates": false,
            "merge-dev": true,
            "merge-extra": false,
            "merge-extra-deep": false,
            "merge-scripts": false
        }
    }
}
```

### Updating sub-levels `composer.json` files

[](#updating-sub-levels-composerjson-files)

In order for composer-merge-plugin to install dependencies from updated or newly created sub-level `composer.json` files in your project you need to run the command:

```
$ composer update --lock

```

This will [instruct Composer to recalculate the file hash](https://getcomposer.org/doc/03-cli.md#update) for the top-level `composer.json` thus triggering composer-merge-plugin to look for the sub-level configuration files and update your dependencies.

Plugin configuration
--------------------

[](#plugin-configuration)

The plugin reads its configuration from the `merge-plugin` section of your composer.json's `extra` section. An `include` setting is required to tell Composer Merge Plugin which file(s) to merge.

### include

[](#include)

The `include` setting can specify either a single value or an array of values. Each value is treated as a PHP `glob()` pattern identifying additional composer.json style configuration files to merge into the root package configuration for the current Composer execution.

The following sections of the found configuration files will be merged into the Composer root package configuration as though they were directly included in the top-level composer.json file:

- [autoload](https://getcomposer.org/doc/04-schema.md#autoload)
- [autoload-dev](https://getcomposer.org/doc/04-schema.md#autoload-dev)(optional, see [merge-dev](#merge-dev) below)
- [conflict](https://getcomposer.org/doc/04-schema.md#conflict)
- [provide](https://getcomposer.org/doc/04-schema.md#provide)
- [replace](https://getcomposer.org/doc/04-schema.md#replace)
- [repositories](https://getcomposer.org/doc/04-schema.md#repositories)
- [require](https://getcomposer.org/doc/04-schema.md#require)
- [require-dev](https://getcomposer.org/doc/04-schema.md#require-dev)(optional, see [merge-dev](#merge-dev) below)
- [suggest](https://getcomposer.org/doc/04-schema.md#suggest)
- [extra](https://getcomposer.org/doc/04-schema.md#extra)(optional, see [merge-extra](#merge-extra) below)
- [scripts](https://getcomposer.org/doc/04-schema.md#scripts)(optional, see [merge-scripts](#merge-scripts) below)

### require

[](#require)

The `require` setting is identical to [`include`](#include) except when a pattern fails to match at least one file then it will cause an error.

### recurse

[](#recurse)

By default the merge plugin is recursive; if an included file has a `merge-plugin` section it will also be processed. This functionality can be disabled by adding a `"recurse": false` setting.

### replace

[](#replace)

By default, Composer's conflict resolution engine is used to determine which version of a package should be installed when multiple files specify the same package. A `"replace": true` setting can be provided to change to a "last version specified wins" conflict resolution strategy. In this mode, duplicate package declarations found in merged files will overwrite the declarations made by earlier files. Files are loaded in the order specified by the `include` setting with globbed files being processed in alphabetical order.

### ignore-duplicates

[](#ignore-duplicates)

By default, Composer's conflict resolution engine is used to determine which version of a package should be installed when multiple files specify the same package. An `"ignore-duplicates": true` setting can be provided to change to a "first version specified wins" conflict resolution strategy. In this mode, duplicate package declarations found in merged files will be ignored in favor of the declarations made by earlier files. Files are loaded in the order specified by the `include` setting with globbed files being processed in alphabetical order.

Note: `"replace": true` and `"ignore-duplicates": true` modes are mutually exclusive. If both are set, `"ignore-duplicates": true` will be used.

### merge-dev

[](#merge-dev)

By default, `autoload-dev` and `require-dev` sections of included files are merged. A `"merge-dev": false` setting will disable this behavior.

### merge-extra

[](#merge-extra)

A `"merge-extra": true` setting enables the merging the contents of the `extra` section of included files as well. The normal merge mode for the extra section is to accept the first version of any key found (e.g. a key in the master config wins over the version found in any imported config). If `replace` mode is active ([see above](#replace)) then this behavior changes and the last key found will win (e.g. the key in the master config is replaced by the key in the imported config). If `"merge-extra-deep": true` is specified then, the sections are merged similar to array\_merge\_recursive() - however duplicate string array keys are replaced instead of merged, while numeric array keys are merged as usual. The usefulness of merging the extra section will vary depending on the Composer plugins being used and the order in which they are processed by Composer.

Note that `merge-plugin` sections are excluded from the merge process, but are always processed by the plugin unless [recursion](#recurse) is disabled.

### merge-scripts

[](#merge-scripts)

A `"merge-scripts": true` setting enables merging the contents of the `scripts` section of included files as well. The normal merge mode for the scripts section is to accept the first version of any key found (e.g. a key in the master config wins over the version found in any imported config). If `replace` mode is active ([see above](#replace)) then this behavior changes and the last key found will win (e.g. the key in the master config is replaced by the key in the imported config).

Note: [custom commands](https://getcomposer.org/doc/articles/scripts.md#writing-custom-commands) added by merged configuration will work when invoked as `composer run-script my-cool-command` but will not be available using the normal `composer my-cool-command` shortcut.

Running tests
-------------

[](#running-tests)

```
$ composer install
$ composer test

```

Contributing
------------

[](#contributing)

Bug, feature requests and other issues should be reported to the [GitHub project](https://github.com/wikimedia/composer-merge-plugin). We accept code and documentation contributions via Pull Requests on GitHub as well.

- [PSR-2 Coding Standard](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md) is used by the project. The included test configuration uses [PHP Code Sniffer](http://pear.php.net/package/PHP_CodeSniffer) to validate the conventions.
- Tests are encouraged. Our test coverage isn't perfect but we'd like it to get better rather than worse, so please try to include tests with your changes.
- Keep the documentation up to date. Make sure `README.md` and other relevant documentation is kept up to date with your changes.
- One pull request per feature. Try to keep your changes focused on solving a single problem. This will make it easier for us to review the change and easier for you to make sure you have updated the necessary tests and documentation.

License
-------

[](#license)

Composer Merge plugin is licensed under the MIT license. See the [`LICENSE`](LICENSE) file for more details.

---

###  Health Score

28

—

LowBetter than 52% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity13

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity61

Established project with proven stability

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~50 days

Recently: every ~1 days

Total

11

Last Release

2002d ago

Major Versions

1.2.0 → 2.0.02021-01-01

### Community

Maintainers

![](https://www.gravatar.com/avatar/303828383a9c2bf382436a61f4471425428b28c095c6df9a9714444cbc163538?d=identicon)[radic](/maintainers/radic)

---

Top Contributors

[![RobinRadic](https://avatars.githubusercontent.com/u/754732?v=4)](https://github.com/RobinRadic "RobinRadic (18 commits)")

###  Code Quality

TestsPHPUnit

Code StylePHP\_CodeSniffer

### Embed Badge

![Health badge](/badges/laradic-composer-merge-plugin/health.svg)

```
[![Health](https://phpackages.com/badges/laradic-composer-merge-plugin/health.svg)](https://phpackages.com/packages/laradic-composer-merge-plugin)
```

###  Alternatives

[symfony/runtime

Enables decoupling PHP applications from global state

74794.9M939](/packages/symfony-runtime)[ergebnis/composer-normalize

Provides a composer plugin for normalizing composer.json.

1.1k40.0M2.6k](/packages/ergebnis-composer-normalize)[drupal/core-composer-scaffold

A flexible Composer project scaffold builder.

5344.1M526](/packages/drupal-core-composer-scaffold)[drupal/core-project-message

Adds a message after Composer installation.

2124.0M193](/packages/drupal-core-project-message)[sandersander/composer-link

Adds ability to link local packages for development with composer

94441.4k](/packages/sandersander-composer-link)[phpro/grumphp-shim

GrumPHP Phar distribution

284.6M333](/packages/phpro-grumphp-shim)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)