Weave Code
Filament Translatable Strings Laravel Package
codedor/filament-translatable-strings
Manage Laravel translation strings directly in Filament. Scan your app for translatable keys, edit values across locales, and keep language files in sync from a clean admin interface—no manual file editing required.
This package manages translatable strings for Laravel in Filament.
Frequently asked questions about Filament Translatable Strings
- What does codedor/filament-translatable-strings do?
- It is a Filament admin-panel plugin for managing Laravel translatable strings. It scans your application for translation keys, lets you edit values across locales, and helps keep language files in sync without manual file editing. It is an admin tool, not a runtime translation engine.
- Which Laravel and Filament versions does this package support?
- The package is built for Laravel applications with Filament, and version 3.0.0 is a dependency-alignment major release that likely targets Filament v4 with newer Laravel and PHP constraints. Exact minimums should be confirmed in the package composer.json and release notes before upgrading. If you are still on Filament v3, stay on package v2.1.2 until your Filament upgrade is complete.
- Is v3.0.0 a breaking change from v2.1.2?
- Yes, treat v3.0.0 as a breaking platform upgrade, not a routine patch. It upgrades wotz/filament-translatable-tabs to v3 and maatwebsite/excel to v4, which can raise Composer constraints and change import/export behavior. Review config and migration changes and test the Filament UI before production.
- How do I install codedor/filament-translatable-strings in a Laravel Filament app?
- Install it with Composer, register the plugin in your Filament panel provider, and run any publish or migration steps documented in the README. Because v3.0.0 pulls major dependencies, run a Composer dry run first to catch resolution conflicts. Pin the version during rollout rather than using a floating constraint.
- Does it require maatwebsite/excel v4?
- In v3.0.0 the package upgrades maatwebsite/excel to v4, so the Excel major is part of the dependency chain in that release. That affects translation import and export workflows and may change file handling behavior. Confirm whether your app uses Excel features and regression-test realistic translation files.
- Can I use this package with Filament v3?
- The evaluation indicates v3.0.0 is aligned with Filament v4, while applications still on Filament v3 should remain on package v2.1.2. Do not force v3.0.0 into a Filament v3 app unless you have verified Composer compatibility. Complete the Filament platform upgrade first, then move the package.
- What should I test before upgrading to v3.0.0?
- Test Composer resolution, the Filament admin UI, locale tabs, translation key scanning, and Excel import and export round-trips in staging. Also check for config or migration changes and confirm existing translation storage still loads correctly. Keep a tested rollback path to v2.1.2 and avoid bundling unrelated Filament upgrades.
- Is this package suitable for production translation management?
- It can be suitable for Laravel and Filament teams that want non-developers to edit localization strings in an admin interface. It is an admin-plane tool, so runtime scaling impact is low, but large Excel imports and exports can be memory- and CPU-intensive. Confirm maintainer responsiveness, test coverage, and release cadence before relying on it for business-critical workflows.
- How does it keep Laravel language files in sync?
- The package scans your application for translatable keys and provides an admin interface to edit values across locales. It then helps sync those values back to language files, reducing manual file editing. Validate the generated files in staging before deploying to production.
- What are alternatives to managing Laravel translations in Filament?
- Alternatives include editing language files manually, using Laravel localization packages, or building custom Filament resources around your translation storage. This package is specifically an admin UI for Laravel translation strings, not a runtime translator. Choose based on whether you need a Filament-native editing workflow versus a broader localization platform.
Weaver
How can I help you explore Laravel packages today?