Why is Magento 2 now such bloatware?

[michel334]

Suggestion:

Make 3rd party modules OPTIONAL and DISABLE by DEFAULT (klarna, dhl, yotpo, dotmailer etc etc etc etc etc)
My clients DO NOT NEED these modules. These modules create bugs, problems and slow loading times.

Make new functionality OPTIONAL and DISABLE by DEFAULT (multi source stock inventory, adobe stock images etc. etc etc..)
My clients DO NOT NEED this functionality. This functionality creates bugs, problems and slow loading times.

I am perfectly capable of choosing the modules my clients need and enabling/installing them if and when we need them.

Also, for the love of all that is holy, no dependency hell :)

Keep it lean and mean guys! :)

Kind regards,
Michel

Summary (*)

Examples (*)

Proposed solution

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• Severity: S0 - Affects critical data or functionality and leaves users with no workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @michel334. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[atishgoswami]

Hello @michel334,

If you want you can remove the extra modules using composer replace functionality.
Here are a few community extensions that can help:

https://github.com/yireo/magento2-replace-tools

Individual Bundles:
https://github.com/yireo/magento2-replace-all
https://github.com/yireo/magento2-replace-bundled
https://github.com/yireo/magento2-replace-inventory
https://github.com/yireo/magento2-replace-core
https://github.com/yireo/magento2-replace-graphql
https://github.com/yireo/magento2-replace-content-staging
https://github.com/yireo/magento2-replace-sample-data

Also additional this module can help identifying we certain modules have any dependencies:
https://github.com/avstudnitz/AvS_DisableModules

Hope this helps 😃

[ericmorand]

I couldn't agree more. Magento 2 is a bloatware, trying to solve everything, slow and incredibly taxing on resources - both from the server and the browser.

But that wouldn't be that bad if it was not a dependency hell: it's impossible to know what modules can be removed because most of them seem to be dependent to another one, even when it's totally non-obvious - see this issue for example: #30501 - and thus it is very difficult and error-prone to remove modules that we don't need.

People keeps on pointing us to composer packages that try to fix the issue but it's not what this issue is about: Magento 2 needs to stop being a bloatware to begin with. Having to install a composer package to remove some modules from Magento 2 is surrealist.

So, here is my proposal:

• Publish every module that are part of Magento 2 base as a discrete Composer package
• Remove all non-legitimate dependencies from these modules
• Publish the framework as a discrete Composer package
• Provide a proper documentation on how to build a Magento 2 application from those discrete packages

Your current approach of providing a out-of-the-box installation (i.e. this very GitHub project) - coming with everything possible - may be appropriate for casual merchants. It is definitely not what professional users need.

[michel334]

@atishgoswami wow thanks, i will try those links. I do appreciate Magento's hard work with all these modules, but i get tired of fixing error's related to modules my clients do not need. Even when modules are "disabled" in the admin i still get errors related to those modules :) But your answer will help, thanks :)

[thomas-kl1]

If you need to start a project without tons of dependencies, you can use your own metapackage, e.g: https://github.com/thomas-kl1/magento2-base-light
This might be harder to upgrade because each dependency need to be check first, but at least there is no "surprise packages"

[duffner]

Hello @michel334,

If you want you can remove the extra modules using composer replace functionality.
Here are a few community extensions that can help:

https://github.com/yireo/magento2-replace-tools

Individual Bundles:
https://github.com/yireo/magento2-replace-all
https://github.com/yireo/magento2-replace-bundled
https://github.com/yireo/magento2-replace-inventory
https://github.com/yireo/magento2-replace-core
https://github.com/yireo/magento2-replace-graphql
https://github.com/yireo/magento2-replace-content-staging
https://github.com/yireo/magento2-replace-sample-data

Also additional this module can help to identify we certain modules have any dependencies:
https://github.com/avstudnitz/AvS_DisableModules

Hope this helps 😃

While I agree this is an option, it shouldn't require a third-party module to disable and should just be disabled not included by default.

[Jieiku]

@thomas-kl1 Is your metapackage the bare minimum to get Magento 2 up and running? using my own meta package sounds like exactly what I might be looking for. I do not want all the modules that got installed by default, I use only 1 of them as far as I am aware, and I would much rather add modules on an as needed basis.

[thomas-kl1]

@Xekon didn't tried in production but I did some tests and it was running fine :) Some packages are still mandatory because of wrong dependencies in the code (some PR are in progress).
Also I've added non mandatory package to the magento2-base-light metapackage such as the developer module. Be aware to specify the elasticsearch package you need.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!