Weave Code
Template I18N Bundle Laravel Package
ruwork/template-i18n-bundle
Symfony bundle that brings internationalization to templates, letting you translate template strings and manage locale-aware content. Integrates with Symfony's translator and Twig to keep multi-language templates clean and organized.
[READ-ONLY] Subtree split of the Ruwork Template I18n Bundle
Frequently asked questions about Template I18N Bundle
- Can I use ruwork/template-i18n-bundle in a Laravel application?
- No. This is a Symfony bundle, not a Laravel package, and it depends on Symfony bundle registration, the DI container compilation pipeline, and likely a Twig extension or templating hook that Laravel does not have. Laravel has no bundle system and no symfony/templating layer, so there is nothing for the package to plug into. Porting it would mean rewriting the entire integration surface, at which point you own all the code anyway.
- What does ruwork/template-i18n-bundle actually do?
- The stated purpose is bringing internationalization to templates so template strings can be translated and locale-aware content managed, integrating with Symfony's translator and Twig. The description is thin, and it is unclear whether the bundle provides per-locale template file resolution, translation-key extraction from templates, a Twig trans filter wrapper, or locale-aware caching. That ambiguity matters, because it determines whether there is any capability worth replicating. Treat the README as uninformative until proven otherwise.
- Is ruwork/template-i18n-bundle still maintained?
- No. The repository is archived and the last release was on 2018-07-20, stopping roughly five Symfony major versions ago. Archived status means there is no upstream patch path, so any defect or security issue becomes yours on day one. There are also zero stars and zero dependents, meaning no production feedback, no issue history to mine, and no one watching for advisories.
- Will Composer let me install this bundle alongside modern Symfony, Twig, or PHP 8?
- Almost certainly not without forcing it. The 2018-era composer.json will pin Symfony, Twig, and PHP ranges that conflict with Symfony 5, 6, or 7 and Twig 2 or 3, so expect hard dependency resolution failures rather than warnings. Using --ignore-platform-reqs or an inline alias just puts 2018 code on PHP 8.x, where removed constructs like each(), curly-brace string offsets, and dynamic properties can fatal. On a Laravel 10 or 11 application this is a non-starter.
- Does Laravel already have template internationalization built in?
- Laravel ships first-class localization: lang/ directories, the __() helper, trans_choice, pluralization, JSON translation keys, and locale switching. That covers translating strings inside Blade views without any extra dependency. What Laravel does not do out of the box is per-locale view file resolution, but that is a roughly 200-line custom view finder, not a dependency-worthy problem.
- How would I replicate per-locale template resolution natively in Laravel?
- Register a custom view finder or extend the existing one so it looks for a locale-specific view path before falling back to the default, then bind it in a service provider. Combined with Laravel's own translator for the string layer, this covers the plausible value of the bundle in well under a day of work. That is a half-day spike plus a small implementation, far cheaper than a compatibility shim. You keep full ownership and zero dependency risk.
- What are the alternatives to this bundle for multi-language templates?
- For Laravel, use the built-in translator and lang files for strings, and a small custom view finder for locale-aware view paths. For Symfony, symfony/translation's own template features and the Twig translation extension are maintained and current. Community locale-aware view finders exist for Laravel as well, though the native approach is usually simpler than adding a package.
- Is the license a reason to fork ruwork/template-i18n-bundle?
- The MIT license is the one clean element here, so forking is legally unencumbered. But forking is not adoption: you would be starting an internal project seeded with a stranger's untested 2018 code. With zero dependents and no issue history, you inherit all the unknowns and none of the support. Reimplementing the idea natively is the better path.
- Does anything in a typical Laravel stack depend on this bundle transitively?
- Unlikely, since the package shows zero dependents and has been archived for years. Still, verify against your own composer.lock files rather than assuming, especially if any legacy Symfony code or shared libraries are in the tree. If nothing references it, there is no migration cost to closing the ticket.
- Should I adopt ruwork/template-i18n-bundle for a new project?
- No. The verdict is do not adopt: wrong framework, archived, 2018 dependency constraints, and no consumer base. The only open question is whether any of its behavior is worth reimplementing natively, and that is a short spike rather than an integration project. Any score suggesting otherwise is an artifact of a heuristic scoring an empty signal set.
Weaver
How can I help you explore Laravel packages today?