Shared on Mage Dispatch · 04 Jul 2025
Why You Should Package Your Modules
The standard way to store Adobe Commerce modules is in the app/code/
Visit link →
https://run-as-root.sh/blog/why-you-should-package-your-modules
More like this
-
https://github.com/opengento/magento2-application
Enables reusing the bootstrap and resetting state between requests, making it compatible with loop HTTP servers like FrankenPHP, Swoole, and ReactPHP (or Fiber). Includes Composer install and setup commands.
65 -
Mage-OShttps://directory.mage-os.org/
Quality-tested catalog of open-source modules with real compatibility checks beyond Composer constraints, vendor trust signals, and editor picks. Filter by compatibility and freshness, and share narrowed views via the address bar.
-
https://github.com/yellowteak/APSB26-146-patches
Pre-split APSB26-146 (VULN-39341) patches tailored for cweagans/composer-patches, organized per 2.4.4-p18 through 2.4.9 with a drop-in patches.json. Covers framework, base, backend, email, and newsletter packages, with steps to apply via Composer.
Mage-OS
New here? This is Mage Dispatch
Mage Dispatch is a community-run archive and bi-weekly newsletter for the Magento, Adobe Commerce and Mage-OS ecosystem. Modules, articles, security advisories and tools, hand-picked by developers and shared so good work does not disappear into the void.
Browse the latest links → Explore by topic → Submit a link → About us →