- How do I install laravel-lang/actions in a Laravel project?
- Run `composer require laravel-lang/actions` to install the package. Then publish the language files with `php artisan vendor:publish --tag=laravel-lang-actions` to make translations available in your `resources/lang` directory.
- Does this package work with Laravel 10 or 11?
- Yes, the package is officially supported for Laravel 8+ and PHP 8.0+. Tested compatibility with Laravel 10 and 11 is maintained through regular updates, but always verify your specific version in the [documentation](https://laravel-lang.com/packages-actions.html).
- Can I override or extend translations for custom actions?
- Absolutely. Create or modify `resources/lang/{locale}/actions.php` to override default translations or add custom keys. The package follows Laravel’s standard language file structure, so your changes will take precedence.
- Will this package slow down my application if I enable many locales?
- The package is lightweight and only loads translations for the active locale by default. For large-scale apps, consider lazy-loading or caching translations via Laravel’s cache system to optimize performance.
- How do I use these translations in Vue.js or React?
- For Vue.js, use `this.$t('actions.key')` with `laravel-vue-i18n`. For React, integrate with `i18next` or fetch translations via Laravel’s API. The package works with any frontend framework as long as you use Laravel’s `__('actions.key')` helper or API endpoints.
- Are the translations for all locales human-verified or machine-translated?
- The package includes 100+ locales, but some (e.g., sa, ug) may be machine-translated. Check the [GitHub repository](https://github.com/Laravel-Lang/actions) for updates or contribute verified translations via the [contribution guidelines](https://laravel-lang.com/contributions.html).
- What happens if a translation key is missing in a locale?
- Laravel’s fallback system kicks in. Configure `app.php` with `'fallback_locale' => 'en'` to default to English if a translation is missing. You can also extend the package’s fallback behavior in your `AppServiceProvider`.
- Do I need to update my CI/CD pipeline for this package?
- Only if you’re publishing language files post-install. Add `php artisan vendor:publish --tag=laravel-lang-actions --ansi` to your deployment script if needed. The package itself doesn’t introduce new CI dependencies.
- Are there alternatives to this package for Laravel localization?
- Yes, alternatives include `spatie/laravel-translatable` for dynamic translations or `backpack/translation-manager` for UI-based management. However, `laravel-lang/actions` is specialized for reusable UI action text (buttons, links) with built-in Laravel integration.
- How can I contribute new translations or fix errors?
- Follow the [contribution guidelines](https://laravel-lang.com/contributions.html) to submit pull requests. Start by forking the repository, adding your translations to `resources/lang/{locale}/actions.php`, and opening a PR. The team actively reviews contributions.