Weave Code
Langsys Php Laravel Laravel Package
langsys/langsys-php-laravel
Laravel integration for LangSys translation management. Adds middleware, helpers, Blade directives, and Artisan commands to fetch, cache, and serve localized strings from LangSys, simplifying multilingual Laravel apps and keeping translations synced with your LangSys project.
Laravel integration for the Langsys translation SDK — service provider, @t Blade directive, locale-detection middleware, Livewire support, and Inertia SSR seeding over langsys/langsys-php.
Frequently asked questions about Langsys Php Laravel
- How do I install langsys/langsys-php-laravel in a Laravel app?
- Install it with Composer using composer require langsys/langsys-php-laravel. The package provides an auto-discovered service provider and facade, so no manual registration is normally required. After installation, publish the configuration file and confirm your Langsys credentials and sync options before running any imports or exports.
- Does this package support Laravel 10, 11, and 12?
- The package is positioned for Laravel 10 through 12 applications that use or are evaluating Langsys. Confirm the exact version constraints in Composer before committing, along with PHP 8.1 or later. If you use Octane or a custom middleware stack, validate lifecycle behavior and middleware ordering in staging first.
- Do I need the ext-intl PHP extension to use Langsys for Laravel?
- Yes, ext-intl is a hard platform prerequisite for this integration. Official php:8.x-fpm images do not bundle it by default, so most containerized deployments need a base-image change or an explicit extension install step. Verify the extension is present in every runtime image, including queue workers and Octane containers.
- What is the difference between tagged mode and automatic response translation?
- Tagged mode uses explicit markers such as the t() helper, the @t Blade directive, and other integration points you apply deliberately. Automatic mode translates HTML responses through optional response middleware. The two coverage modes are intended to be mutually exclusive per project, because running both can re-register translated output as source phrases and pollute the shared Langsys catalog.
- How do I configure Langsys API credentials and sync options?
- Configuration is publishable, and the package includes settings for API credentials and sync behavior. The release notes do not detail the exact configuration keys, credential handling, endpoint overrides, or queue behavior, so confirm those in the package source before commitment. Keep credentials out of version control and use environment-specific values in staging and production.
- Can I use @t and t() alongside Laravel's __() helper in Blade?
- Yes, the package is designed to coexist with Laravel's localization conventions and the __() helper. It adds a t() helper and an @t Blade directive for fetching Langsys strings directly in templates. Apply them to a bounded pilot surface first so you can verify registration behavior before expanding coverage.
- How does Langsys caching work, and will it keep runtime fast?
- The package uses cache-aware locale loading to keep runtime lookups fast and fits Laravel's existing caching conventions. Cache TTL, timeout, retry, and invalidation semantics are not detailed in the release notes and need to be confirmed before production rollout. Validate cache behavior in staging, especially when translations change frequently or when queue workers and web requests share a cache store.
- Does langsys/langsys-php-laravel work with Inertia SSR and the Langsys JavaScript SDK?
- The package includes InertiaSsrProps::share() for sharing translation props through Inertia SSR. Hydration and SSR scenarios depend on langsys-js-typescript version 0.6.2 or later, alongside langsys/langsys-php ^1.3. Only add the Inertia sharing helper if your application actually uses Inertia SSR, since otherwise it adds unnecessary complexity.
- Is automatic HTML response translation safe for production?
- Automatic response translation is high-leverage but invasive, and it should be treated as a later project after tagged mode is proven. It can affect latency, response size, streamed or compressed responses, Alpine-injected text, exclusion discipline, and PII exposure if rendered content is registered. Start with tagged mode in a non-critical Laravel surface, keep TranslateResponse disabled, and define exclusions and catalog-cleanup plans before enabling it.
- Is langsys/langsys-php-laravel production ready after its v1.0.0 release?
- The available assessment is an initial review based on v1.0.0 release notes only, with no code audit or benchmarks, so treat it as a conditional pilot rather than a proven production dependency. Pin PHP, Laravel, and package versions, validate registration and fallback behavior in staging, and confirm the support and upgrade policy before committing. A sensible first step is tagged mode on a bounded Blade or Inertia surface, with automatic translation and Octane-specific behavior validated separately.
Weaver
How can I help you explore Laravel packages today?