- How do I install dusanbre/laravel-tolgee in a Laravel application?
- Install it with Composer using dusanbre/laravel-tolgee, then check the README for any service provider or config publishing step. Laravel package auto-discovery may register the provider automatically, but you should verify this in your app. Confirm the package's Laravel and PHP version constraints in composer.json before installing.
- Does laravel-tolgee support Laravel 10, Laravel 11, and PHP 8.1+?
- The package targets Laravel applications and is installed through Composer, but the provided assessment does not confirm exact Laravel and PHP version constraints. Check the package composer.json for require and require-dev constraints before upgrading. Test it against your target Laravel 10 or 11 and PHP 8.1+ environment, especially if you rely on custom translation paths.
- How do I configure Tolgee API credentials and project ID for laravel-tolgee?
- Expect a published configuration file where you set Tolgee API credentials, project or endpoint details, and local translation paths. The exact config keys are not listed in the assessment, so inspect the published config and README after installation. Store tokens in environment variables and avoid committing Tolgee secrets to source control.
- What changed in laravel-tolgee v1.1.0 for TolgeeService path handling and formatting?
- v1.1.0 refactors TolgeeService to improve path handling and formatting, but the assessment does not include exact behavior details. Treat this as a behavioral change around which translation files are read or written and how keys or values are formatted. Regression-test file discovery, path normalization, and generated output before production rollout.
- Is laravel-tolgee v1.1.0 backward compatible with v1.0.x config files and published assets?
- It is a minor release, but the TolgeeService refactor can still affect path resolution and formatting behavior. No migration guide is mentioned, so pin v1.0.9 in staging and test v1.1.0 against your existing config. Diff generated translation files before and after the upgrade and verify published assets still work.
- How do I sync translations between Tolgee and Laravel lang files with this package?
- The package is intended to export and import translation keys, pull remote translations into local storage, and push local changes to Tolgee. Configure your Tolgee credentials, project details, and local translation paths, then use the service or commands documented by the package. Validate the generated Laravel lang files and decide whether Tolgee is the source of truth or a downstream sync target.
- Can laravel-tolgee handle Blade and PHP translation files?
- The package description says it supports PHP and Blade projects, localization workflows, and in-context translation editing. It is designed to manage Laravel translation files rather than replace Laravel's native translation loader. Test your specific PHP array files, JSON translations, Blade usage, and any package translation namespaces against the package behavior.
- How are Tolgee API failures surfaced by laravel-tolgee: exceptions, logs, or silent fallbacks?
- The assessment does not specify whether Tolgee API failures throw exceptions, are logged, or fall back silently. Inspect the service code and README for error-handling behavior before relying on it in production. Test invalid credentials, network timeouts, and missing projects in staging, and add monitoring around sync commands if failures are not explicit.
- What should I test after upgrading laravel-tolgee to v1.1.0?
- Test translation file discovery, path normalization, nested language directories, Windows-style paths, custom translation locations, and Laravel package translation namespaces. Compare generated files against v1.0.9 and verify output formatting and key ordering. Also check custom code that subclasses or directly calls TolgeeService, because public behavior may have changed.
- Is laravel-tolgee actively maintained, and should I adopt it for Tolgee integration?
- v1.1.0 includes a Dependabot CI action bump and a first-time contributor refactor, but active maintenance beyond this release is not confirmed. It is a reasonable fit for Laravel teams already using Tolgee or evaluating it as a translation management platform. Do not adopt it solely for local translation management, because it adds a remote Tolgee dependency without replacing Laravel's built-in translation loader.