Download the PHP package lloc/composer-i18n-scripts without Composer
On this page you can find all versions of the php package lloc/composer-i18n-scripts. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download lloc/composer-i18n-scripts
More information about lloc/composer-i18n-scripts
Files in lloc/composer-i18n-scripts
Package composer-i18n-scripts
Short Description Simplify the internationalization of your WordPress plugin or theme using WP-CLI — powered by Composer.
License GPL-2.0-or-later
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package composer-i18n-scripts
Composer i18n Scripts
Automate the internationalization workflow of your WordPress plugin or theme by wiring WP-CLI translation tools into familiar Composer commands.
Requirements
- PHP 7.4+ and Composer 2.6+ (Composer plugin API 2.6 is required)
- WP-CLI 2.12+ available on your
$PATH - A WordPress plugin or theme with
Text DomainandDomain Pathheaders defined
Installation
Composer automatically registers the plugin; no manual bootstrap code is needed. Running composer install on the project will keep the plugin active for all contributors.
Configuration
The plugin inspects your project root to infer settings:
- Themes: reads
style.css - Plugins: reads the main plugin file (matching the directory name or
index.php)
Provide headers like the following so WP-CLI receives the right text domain and language directory:
If no metadata is found, defaults are Text Domain: messages and Domain Path: /languages.
Usage
Run the commands from the WordPress project root so that wp can load your environment.
| Command | Purpose |
|---|---|
composer i18n:make-pot |
Scan the source directory and generate languages/<domain>.pot. |
composer i18n:create-po <locale> |
Copy the .pot file to a locale-specific .po file (e.g. de_DE). |
composer i18n:update-po |
Merge the current .pot changes into every .po in languages/. |
composer i18n:make-mo |
Compile all .po files into .mo binaries. |
composer i18n:make-php |
Export .po translations into PHP array files for performance-sensitive setups. |
composer i18n:make-json |
Build JavaScript translation catalogs (*.json) without purging existing assets. |
Example workflow:
Development
composer install– install dependencies and register the plugincomposer qa– PHPCS (WordPress Coding Standards) + PHPStan level 10composer tests– run PHPUnit suite undertests/Commandscomposer tests:coverage– generate HTML coverage intests/coverage/composer cs:fix– automatically fix style violations
Refer to AGENTS.md for contributor conventions, coding standards, and pull request expectations.
Troubleshooting
- “Text domain is not set”: ensure your plugin/theme headers declare
Text DomainandDomain Path. - WP-CLI not found: verify
wpis installed globally or provide an absolute path (e.g. symlinkwpinto/usr/local/bin). - Translations not picking up new strings: rerun
composer i18n:make-potbefore updating.pofiles so the template is up to date.
