PHPackages yireo/magento2-replace-tools - 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. yireo/magento2-replace-tools ActiveComposer-plugin[Utility & Helpers](/categories/utility) yireo/magento2-replace-tools ============================ Tools to maintain yireo/magento2-replace packages 1.0.7(1y ago)11796.5k↓40.6%20[5 issues](https://github.com/yireo/magento2-replace-tools/issues)[2 PRs](https://github.com/yireo/magento2-replace-tools/pulls)OSL-3.0PHPCI failing Since Oct 21Pushed 1y ago7 watchersCompare [ Source](https://github.com/yireo/magento2-replace-tools)[ Packagist](https://packagist.org/packages/yireo/magento2-replace-tools)[ RSS](/packages/yireo-magento2-replace-tools/feed)WikiDiscussions master Synced 2d ago READMEChangelog (8)Dependencies (7)Versions (10)Used By (0) Magento Composer Replacement Tool ================================= [](#magento-composer-replacement-tool) **This repository offers a composer plugin to help you manage composer replacements in your root `composer.json`. Once this package is installed, the composer plugin is installed, which allows you to manage replacements via specific commands (`composer replace:?`). To make sure replacements don't conflict, this plugin adds its own section `extra.replace` to your `composer.json` as well.** Quickstart ---------- [](#quickstart) ``` composer require yireo/magento2-replace-tools --dev # Require this plugin composer replace:bulk:add yireo/magento2-replace-bundled # Add a replacement bulk package composer replace:build # Rebuild your composer.json based upon this composer update --lock # Actually update all your dependencies ``` Installation of this plugin --------------------------- [](#installation-of-this-plugin) ``` composer require yireo/magento2-replace-tools --dev ``` General usage ------------- [](#general-usage) Through a series commands, this composer plugin aims to help you manage your `replace` section more efficiently. Instead of individually adding packages, packages are added in bulk through an additional composer section `extra.replace`: ``` { "replace": { "klarna/module-kp-graph-ql": "*", "magento/module-async-order-graph-ql": "*", "magento/module-authorizenet-graph-ql": "*", "magento/module-braintree-graph-ql": "*", "magento/module-bundle-graph-ql": "*", "magento/module-catalog-graph-ql": "*", ... "yireo/example-graph-ql" }, "extra": { "replace": { "bulk": [ "yireo/magento2-replace-graph-ql" ], "exclude": { "magento/module-graph-ql": "*" }, "include": { "yireo/example-graph-ql": "*" } } } } ``` Replacing packages (any composer project) ----------------------------------------- [](#replacing-packages-any-composer-project) List all current composer replacements: ``` composer replace:list ``` Replace a specific package: ``` composer replace:add foo/bar '2.0' ``` Remove a specific replacement: ``` composer replace:remove foo/bar ``` Remove a specific package (by using a version set to `*`): ``` composer replace:add foo/bar ``` Exclude a specific package from the replace section (so include the package when installing): ``` composer replace:exclude foo/bar ``` Include a specific package from the replace section (override a package that has been added to the replace list by a bulk package): ``` composer replace:include foo/bar ``` Replacing packages by bulk (Magento-specific) --------------------------------------------- [](#replacing-packages-by-bulk-magento-specific) Replace all Magento Multi Source Inventory packages: ``` composer replace:bulk:add yireo/magento2-replace-inventory ``` This adds all replacements from this meta-package `yireo/magento2-replace-inventory` to your own `replace` section. And it also adds an additional section like the following: ``` "extra": { "replace": { "bulk": [ "yireo/magento2-replace-inventory" ] } }, ``` Replace all Magento GraphQL packages, but not the `magento/module-graph-ql` package itself, but again also replacing a package `yireo/example-graph-ql`: ``` composer replace:bulk:add yireo/magento2-replace-graphql composer replace:exclude magento/module-graph-ql composer replace:include yireo/example-graph-ql composer replace:validate composer replace:build ``` This adds all replacements from this meta-package `yireo/magento2-replace-graphql` (except the package `magento/module-graph-ql` but including the package `yireo/example-graph-ql`) to your own `replace` section. And it also adds an additional section like the following: ``` { "replace": { "klarna/module-kp-graph-ql": "*", "magento/module-async-order-graph-ql": "*", "magento/module-authorizenet-graph-ql": "*", "magento/module-braintree-graph-ql": "*", "magento/module-bundle-graph-ql": "*", "magento/module-catalog-graph-ql": "*", ... "yireo/example-graph-ql" }, "extra": { "replace": { "bulk": [ "yireo/magento2-replace-graph-ql" ], "exclude": { "magento/module-graph-ql": "*" }, "include": { "yireo/example-graph-ql": "*" } } } } ``` ### Note about `replace:build` [](#note-about-replacebuild) ⚠️ Warning: Due to the nature of its implementation, `replace:build` will replace your existing `replace` section in `composer.json`. If you replaced any individual dependencies here, make sure to re-add them after `replace:build`. At the moment this composer extension does not maintain the existing `replace` section of your `composer.json`. If you want to have this tool to manage this individual dependency for you, use the `extra.replace.include` section (see above). Available bulk packages ----------------------- [](#available-bulk-packages) - [yireo/magento2-replace-bundled](https://github.com/yireo/magento2-replace-bundled) removes third party bundled extensions - [yireo/magento2-replace-content-staging](https://github.com/yireo/magento2-replace-content-staging) removes optional Content Staging modules - [yireo/magento2-replace-core](https://github.com/yireo/magento2-replace-core) removes optional core modules - [yireo/magento2-replace-graphql](https://github.com/yireo/magento2-replace-graphql) removes optional GraphQL modules - [yireo/magento2-replace-inventory](https://github.com/yireo/magento2-replace-inventory) removes optional MSI modules - [yireo/magento2-replace-sample-data](https://github.com/yireo/magento2-replace-sample-data) removes sample data modules - [yireo/magento2-replace-all](https://github.com/yireo/magento2-replace-all) removes all packages listed in the other directories Please note that the `replace` feature of composer as being used in these repositories is not well documented and probably abused a bit. If you are not willing to invest time to troubleshoot this yourself, please forget about this approach entirely so that we don't waste anyones time. ### Building composer replacements [](#building-composer-replacements) Use the following command to configure your `composer.json` for using bulk replacements: ``` composer replace:bulk:add yireo/magento2-replace-bundled composer replace:bulk:add yireo/magento2-replace-inventory composer replace:bulk:add yireo/magento2-replace-graphql composer replace:bulk:add yireo/magento2-replace-sample-data composer replace:validate composer replace:build ``` ### Using composer replacements [](#using-composer-replacements) Once you have a `replace` section in your composer.json file ``` rm -r vendor/ composer update --lock ``` Do not just use `composer install`. Do not use regular composer commands, but please follow this procedure literally and to the point. After having replaced Magento composer packages ----------------------------------------------- [](#after-having-replaced-magento-composer-packages) After you have installed a composer replacement, make sure to wipe out the `generated/` folder first and next, run `bin/magento setup:di:compile` and `bin/magento setup:upgrade` to see if Magento still works. Please note that these steps are generic developer steps, not related to this repository. ``` rm -r generated/ bin/magento setup:di:compile bin/magento setup:upgrade ``` Sample for Hyva Themes ---------------------- [](#sample-for-hyva-themes) The following shows an example configuration section for your `composer.json`: ``` { "extra": { "replace": { "bulk": [ "yireo/magento2-replace-core", "yireo/magento2-replace-content-staging", "yireo/magento2-replace-inventory", "yireo/magento2-replace-bundled", "yireo/magento2-replace-graphql", "yireo/magento2-replace-sample-data" ], "exclude": { "magento/module-graph-ql": "*", "magento/module-graph-ql-cache": "*", "magento/module-catalog-graph-ql": "*", "magento/module-customer-graph-ql": "*", "magento/module-eav-graph-ql": "*", "magento/module-sales-graph-ql": "*", "magento/module-quote-graph-ql": "*" }, "include": { "magento/module-admin-graph-ql-server": "*", "magento/module-graph-ql-server": "*", "magento/page-builder": "*", "magento/module-service-proxy": "*", "magento/services-connector": "*", "magento/services-id": "*", "magento/module-services-id-graph-ql-server": "*", "magento/module-services-id-layout": "*", "magento/payment-services": "*" } } } } ``` FAQ --- [](#faq) #### I try to install this with `composer require a/b` but get errors [](#i-try-to-install-this-with-composer-require-ab-but-get-errors) Please note that this kind of question is not going to be answered anymore, except here: Do **not** use a simple `composer require a/b` command. It is not documented above, it is not part of the procedure and it does not work. Do not reason that if you know composer, you know that a simple `composer require a/b` must work. If you think composer replacements are installed the way as composer packages, you do not know composer replacements. If you want to receive support, follow along with **all** of the commands outlined above. And stick to it. Don't argue, don't reason, but stick with it. Next, if all of the workarounds with composer commands fail, only then report an issue on GitHub. #### Your extension does not work [](#your-extension-does-not-work) You are damn right it does not! The reason is that it is not an extension. This is **not** about installing Magento modules. This is about replacing composer packages with nothing. The *extension* is not there, it is not a Magento module. It is rather a carefully crafted composer configuration that could be copied manually or installed with the right procedure. It is a composer meta-package with an undocumented trick. If you don't like it, don't use it. #### Installing a package leads to many errors [](#installing-a-package-leads-to-many-errors) Intruiging, isn't it? Yes, this could happen. Perhaps some modules that you are replacing are in use with your own custom code. Or perhaps you are relying on other third party extensions that have yet an undocumented dependency that conflicts with this `replace` trick. If you are not willing to troubleshoot this, simply skip this trick and move on. If you are willing to troubleshoot this, copy the `replace` lines to your own `composer.json` and remove lines one-by-one until you have found the culprit. #### Is a certain package compatible with Magento 2.x.y? [](#is-a-certain-package-compatible-with-magento-2xy) Theoretically, yes. Make sure to understand that these packages are not modules, not libraries, not Magento extensions. It is a gathering of hacks. So, if you understand the benefit of the `replace` trick in composer, you can use these repository to ease the pain of upgrading. One conceptual idea in these repositories is to try to keep track of the main Magento version by creating a branch `2.x.y` with a corresponding release `x.y.z`. So, Magento 2.3.5 matches with the replace branch `3.5.*`. Magento 2.4.1 matches with the replace branch `4.1`. By adding a dependency with `^4.0` in your `composer.json`, this will automatically upgrade to any `4.X` version, but exclude a major bump to `5.X`. Sometimes the actual work falls behind, which by no means indicates that the current bundling of tricks no longer works. Simply, install this package using `composer` and see if this works for you (see below). #### How do I upgrade the replacements to Magento 2.4.X? [](#how-do-i-upgrade-the-replacements-to-magento-24x) Please note the above on the versioning strategy. Once that's understood, the actual implementation is simple: `composer require yireo/magento2-replace-core:^4.0 --no-update`. #### How to test if this is working? [](#how-to-test-if-this-is-working) Take your test environment. Install the relevant packages. If this works, run `bin/magento setup:di:compile` (in both Developer Mode and Production Mode) to see if there are any errors. If this fails, feel free to report an issue here. If this works, you could assume that this works ok. Remember this repository offers a smart hack, not a supported solution. You can also live with a slower Magento installation that fully complies with the Magento standards (and ships with modules you don't use and/or like). #### How do I know if something is replaced? [](#how-do-i-know-if-something-is-replaced) Unfortunately, composer does not offer a CLI for this and because the replacements are stored in these packages, they are not mentioned in your own projects `composer.json` (unless you put them there). However, by opening up the `composer.lock` file and searching for the keyword `replace` you can see which packages are replaced by all packages in your installation. A simple `composer show yireo/magento2-replace-bundled` shows which replacements are included in a specific package. ### Health Score 42 — FairBetter than 88% of packages Maintenance34 Infrequent updates — may be unmaintained Popularity48 Moderate usage in the ecosystem Community21 Small or concentrated contributor base Maturity53 Maturing project, gaining track record Bus Factor1 Top contributor holds 93.9% 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 ~57 days Recently: every ~81 days Total 8 Last Release 654d ago ### Community Maintainers ![](https://avatars.githubusercontent.com/u/1373981?v=4)[Yireo](/maintainers/yireo)[@yireo](https://github.com/yireo) --- Top Contributors [![jissereitsma](https://avatars.githubusercontent.com/u/7670482?v=4)](https://github.com/jissereitsma "jissereitsma (92 commits)")[![JoostWan](https://avatars.githubusercontent.com/u/5435412?v=4)](https://github.com/JoostWan "JoostWan (1 commits)")[![henkvalk](https://avatars.githubusercontent.com/u/8955854?v=4)](https://github.com/henkvalk "henkvalk (1 commits)")[![peterjaap](https://avatars.githubusercontent.com/u/431360?v=4)](https://github.com/peterjaap "peterjaap (1 commits)")[![riconeitzel](https://avatars.githubusercontent.com/u/930706?v=4)](https://github.com/riconeitzel "riconeitzel (1 commits)")[![superdav42](https://avatars.githubusercontent.com/u/1534605?v=4)](https://github.com/superdav42 "superdav42 (1 commits)")[![Justin991q](https://avatars.githubusercontent.com/u/4533867?v=4)](https://github.com/Justin991q "Justin991q (1 commits)") --- Tags magento2 ### Code Quality TestsPHPUnit ### Embed Badge ![Health badge](/badges/yireo-magento2-replace-tools/health.svg) ``` [![Health](https://phpackages.com/badges/yireo-magento2-replace-tools/health.svg)](https://phpackages.com/packages/yireo-magento2-replace-tools) ``` ### Alternatives [laravel/framework The Laravel Framework. 34.8k543.8M20.1k](/packages/laravel-framework)[shopware/core Shopware platform is the core for all Shopware ecommerce products. 585.6M574](/packages/shopware-core)[shopware/platform The Shopware e-commerce core 3.4k1.5M3](/packages/shopware-platform)[tempest/framework The PHP framework that gets out of your way. 2.2k34.4k15](/packages/tempest-framework)[brianhenryie/strauss Prefixes dependencies namespaces so they are unique to your plugin 190438.1k36](/packages/brianhenryie-strauss)[spatie/laravel-export Create a static site bundle from a Laravel app 674146.0k6](/packages/spatie-laravel-export) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)