Weave Code
I18N Routing Bundle Laravel Package
financeua/i18n-routing-bundle
Internationalized routing bundle for Laravel/PHP apps, adding locale-aware route generation and URL handling so your application can serve translated, language-prefixed routes with minimal configuration.
Full routing internationalized on your Symfony project
Frequently asked questions about I18N Routing Bundle
- Can I install financeua/i18n-routing-bundle in a Laravel app?
- No. It is a Symfony bundle that depends on Symfony Routing, HttpKernel, and DependencyInjection, and it expects a Symfony kernel and service container. Laravel uses Illuminate\Routing with a different registrar and URL generator, so there is no integration point. Treat the package as a design reference, not a Composer dependency for Laravel.
- Is financeua/i18n-routing-bundle a Laravel package?
- No, despite catalog listings describing it as a Laravel/PHP package. It is BeSimpleI18nRoutingBundle for Symfony. The Laravel label is a metadata mismatch, not a product signal. For Laravel, use native locale route groups or a maintained localization package instead.
- How do I create locale-prefixed routes in Laravel without this bundle?
- Wrap your routes in a group with a {locale} prefix and constrain locale to supported values. Resolve the active locale in middleware and generate URLs with route('products.index', ['locale' => app()->getLocale()]). This covers paths like /en/products and /fr/products without a third-party routing bundle.
- What Laravel packages replace BeSimpleI18nRoutingBundle for localized URLs?
- mcamara/laravel-localization and codezero/laravel-localized-routes are the common maintained options. mcamara handles locale prefixes, detection, and localized route generation, while codezero focuses on translated path segments. Choose based on whether you need prefix-only URLs or translated slugs. Evaluate maintenance and Laravel version support before adopting either one.
- Does this bundle support translated path segments like /fr/produits?
- Yes, that is its core pattern: one route definition with per-locale translated path segments and locale detection. But the implementation is Symfony-specific and not portable as code. In Laravel, the equivalent is codezero/laravel-localized-routes or a first-party slug map keyed by locale. The design is reusable; the bundle itself is not.
- How does locale detection work in this bundle versus Laravel?
- The bundle detects locale from the request path and integrates with Symfony's routing and translator services. Laravel does not share that pipeline, so you would implement detection in middleware. Inspect the first path segment, validate it against supported locales, call app()->setLocale(), and redirect or fall back to the default. Native route prefixes plus middleware reproduce the behavior.
- Is financeua/i18n-routing-bundle safe for production?
- Treat it as high risk for a Laravel application. It is a Symfony bundle with no Laravel compatibility, and the parent project appears abandoned with no dependents or community fixes. Routing is the seam every URL passes through, so stale routing code carries high blast radius. Do not put it in a customer-facing or SEO-sensitive path.
- What Laravel versions does this package support?
- It does not target Laravel at all. It is built for Symfony's routing and kernel components, so Laravel version support is not applicable. If you need Laravel 10 or 11 localization, use a package that explicitly declares support for those versions. Verify compatibility in the package's composer.json before any design work.
- How do I generate localized URLs in Blade instead of Twig?
- This bundle provides Twig helpers for localized URL generation, which do not apply to Blade. In Laravel, use route() with the locale parameter or a helper from mcamara/laravel-localization such as LaravelLocalization::getLocalizedURL(). Keep route names stable across locales and pass the active locale explicitly. That gives templates a single, locale-aware URL call.
- Should I port this Symfony bundle's logic to Laravel or use an existing package?
- Start with the requirement, not the code. If you only need locale prefixes, native route groups plus middleware are enough; if you need translated path segments, evaluate codezero/laravel-localized-routes before building. Port only the design ideas, such as per-locale slug maps, default-locale fallback, and canonical and hreflang alignment. A maintained dependency is usually cheaper than porting an abandoned bundle.
Weaver
How can I help you explore Laravel packages today?