yireo / magento2-additional-language-file
yireo/magento2-additional-language-file
Yireo AdditionalLanguageFile
This Magento 2 module adds the ability to add an extra language file to
your theme.
Overview
Every theme has the ability to override language strings in a file like
i18n/en_US.csv. This module allows you to add a second file
i18n/en_US_additional.csv which is loaded on top of the original file.
The benefit of this is that you can have a parent theme that fills up
the en_US.csv which is then inherited in the child theme. Yet using
this module, you can make specific overrides in the additional language
file.
Installation
Install this module within Magento 2 using composer:
composer require yireo/magento2-additional-language-file
And of course afterwards use the regular commands to enable the module.
Technical architecture
This module remaps the preference for the original Magento\Framework\Translate file to a new class.
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.1] - 22 October 2025
Fixed
- Add new CI files
- Note on PWA
- Coding style
- Fix homepage
- Increase requirements
- Update README.md
[0.0.1] - 22 October 2025
Added
- Initial release
Requires 2
| Package | Constraint |
|---|---|
| magento/framework | ^100.0|^101.0|^102.0|^103.0 |
| php | >=7.0.0 |
Requires-dev 2
| Package | Constraint |
|---|---|
| composer/composer | *@dev |
| phpunit/phpunit | * |
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.
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.
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 vendorReplace bundled third party packages from Magento
N/A
Turn 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.