Weave Code
Translation Laravel Package
waavi/translation
Waavi Translation is a Laravel package that stores and manages translations in the database instead of flat files. It adds caching, file import/export, a translator service, and fallback support so you can edit language strings at runtime without redeploying.
A Translation package for Laravel 5 with database and cache support
Frequently asked questions about Translation
- What is waavi/translation used for in Laravel?
- waavi/translation is a Laravel 5 package that stores and manages translations in a database instead of flat language files. It adds caching, file import and export, a translator service, fallback support, and runtime-editable language strings. It is intended for legacy Laravel 5 applications that need translations changed without redeploying.
- How do I install waavi/translation in a Laravel 5 application?
- Install it with Composer, then publish its config and migrations and import your existing lang files. You also need to configure locale detection and route translation reads through the package, often using its service provider, facade, models, and locale middleware. Integration is moderate and should be tested in a non-critical environment first.
- Which Laravel and PHP versions does waavi/translation support?
- The package is purpose-built for Laravel 5 and does not align with modern Laravel or Symfony translation contracts. It carries old PHP and Laravel constraints, so you must verify Composer requirements against your exact stack. It is not a fit for Laravel 6 and above or greenfield applications.
- Is waavi/translation still maintained?
- The evaluation shows no meaningful adoption signals, zero dependents, and no visible stars, and the package appears unmaintained. It ties applications to an end-of-life framework and lacks security patching. Expect to fork or vendor it, own security review, and manually track compatibility if you keep it.
- How does waavi/translation handle cache invalidation across multiple app nodes?
- The package adds cache support, but multi-node deployments need a centralized cache such as Redis or Memcached plus a reliable invalidation strategy. Admin edits must invalidate cached translations consistently, otherwise nodes can serve stale UI copy. Cold caches create database hits and possible cache stampedes, so plan warm-up and load testing.
- Does waavi/translation support pluralization, ICU messages, JSON translations, and validation messages?
- Because the package replaces Laravel's native translation loader and repository, you must explicitly test pluralization, validation messages, JSON translations, and fallback behavior rather than assume parity. The evaluation flags fallback, pluralization, and cache consistency as risk areas. ICU message support is not documented in the provided context, so verify it before relying on it.
- Can I import and export existing Laravel lang files with waavi/translation?
- Yes, the package includes file import and export functionality. For a legacy application, inventory your existing lang files, import a small controlled subset, and run the package in parallel with file-based translations to compare output before cutover. Confirm safe round-tripping and keep file-based fallback available during rollout.
- Is waavi/translation suitable for multi-tenant or per-domain translations?
- Multi-tenant and per-domain translation storage are not documented in the provided context, so do not assume native support. The database-backed design could be customized, but that increases maintenance and migration risk. Treat it as an internal customization that must be proven before production use.
- What are the best alternatives to waavi/translation for Laravel?
- For modern Laravel, prefer native lang files or a maintained package such as spatie/laravel-translation-loader. For a legacy Laravel 5 app, avoid adopting waavi/translation for new work and isolate translation access behind an internal interface if it is already present. Plan replacement rather than expanding dependence on an unmaintained package.
- What production risks should I consider before using waavi/translation?
- Risk is high: database outages or migration drift can break translation loading, cache stampedes can spike database load, stale cache after edits causes inconsistent UI copy, and locale middleware misconfiguration can serve the wrong language. Keep file-based fallback available, test rollback and fallback behavior, and document a replacement or exit plan. Vendor or fork the package if you must run it in production.
Weaver
How can I help you explore Laravel packages today?