yireo / yireo_devhacks
yireo/yireo_devhacks
Some hacks to make M2 development easier
Yireo DevHacks
Magento 2 module with development hacks, that came in handy for myself.
Installation
Use the following commands to install:
composer require yireo/magento2-devhacks:@dev --dev
Enable this module:
./bin/magento module:enable Yireo_DevHacks
./bin/magento setup:upgrade
Skip template path validation
The core checks whether PHTML templates are in the path of the Magento core. When using the composer feature path to symlink a local repository to Magento, while the path is outside of Magento, this throws an exception. This module simply skips the entire logic. No configuration needed. Bam.
Toggle TESTS_CLEANUP in integration tests configuration
Moved to separate Yireo_IntegrationTestHelper module instead.
Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
[Unreleased]
[0.1.3] - 22 October 2025
Fixed
- Add hacked copy of File
- Remove old hacks
- Add dev keyword
- Make exception on empty templates more readable
- Symfony 6 compliance
- Add new override
- Remove integration test CLI
- Add very simple live test
[0.1.2] - 2021-05-13
Fixed
- Fix new path validator by using "hack files"
[0.1.1] - 2020-07-29
Fixed
- Fixed 2.4 compatibility
[0.1.0] - 2019-04-28
Added
- Toggle TESTS_CLEANUP in integration tests configuration
[0.0.1] - 2019-03
Added
- Skip template path validation
| Version | Stability | QA Status | Compatibility | Released |
|---|---|---|---|---|
| 0.1.3 | stable | Fail | Magento 2.4.7-2.4.9 Details | 2025-10-22 11:43:30 |
| 0.1.2 | stable | Not tested | Not yet tested Details | 2021-05-13 09:33:28 |
| 0.1.1 | stable | Not tested | Not yet tested Details | 2020-07-29 08:56:18 |
| 0.1.0 | stable | Not tested | Not yet tested Details | 2019-04-28 07:14:36 |
Requires 3
| Package | Constraint |
|---|---|
| ext-pcre | * |
| magento/framework | ^100.0|^101.0|^102.0|^103.0 |
| php | >=7.2.0 |
Compatibility
Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.
Code Quality
Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge — a phpcs finding can't make a module incompatible.
Static analysis
Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.
| Tool | Status | Findings | Summary |
|---|---|---|---|
| PHPCS | Fail | 82 | 33 errors, 49 warnings (ruleset: Magento2) — 2 auto-fixable with phpcbf |
| PHPMD | Warning | 47 | 47 rule violations (ErrorControlOperator:34, MissingImport:7, UnusedFormalParameter:3, ExcessiveClassLength:1, TooManyMethods:1) |
| Cpd | Pass | 0 | |
| Composer validate | Info | 1 | valid; 1 advisory note (composer validate --strict) |
PHPStan
Type-checks the module's PHP against a real Magento install at the configured gate level. Re-runs per Magento and PHP version because resolvable symbols differ between releases. Cell → details modal.
Tests
Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.
Unit tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Integration tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Security
Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.
More from yireo
View vendorTurn an existing module into recurring revenue.
If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.