Weave Code
Locale Bundle Laravel Package
forci/locale-bundle
forci/locale-bundle is a PHP locale management bundle for multilingual applications. It provides locale configuration and detection utilities to help route users to the right language and integrate localized content, making it easier to build and maintain localized experiences.
Simple locale management for Symfony3/4
Frequently asked questions about Locale Bundle
- Is forci/locale-bundle compatible with Laravel?
- No. It is a Symfony bundle, and Laravel does not implement the Symfony bundle contract: there is no registerBundles(), no extension auto-loading, and no compiler-pass pipeline. Laravel consumes Symfony components such as HttpFoundation and Routing, but it does not run Symfony bundles. Installing it in a Laravel app will not make its locale detection or switching work out of the box.
- Can I install forci/locale-bundle in a Laravel project with Composer?
- You may be able to force an install, but it is not a supported integration. A Symfony 3/4-era bundle will constrain symfony/framework-bundle to the ^3 or ^4 range, while modern Laravel ships Symfony 6/7 components, so Composer will usually refuse resolution or require replace or alias hacks. Those hacks destabilize your dependency graph to obtain a feature Laravel already provides natively.
- What does forci/locale-bundle actually do?
- It is a Symfony bundle for locale detection and switching in multilingual applications. It resolves a locale from the request, session, or browser headers, supports configurable fallbacks, and provides route- and URL-based switching helpers plus Twig integration. The concepts are familiar, but the delivery mechanism is Symfony-specific and does not map onto Laravel's middleware and translator architecture.
- How do I detect a user's preferred language in Laravel without this bundle?
- Use Laravel's request helpers and locale API. $request->getPreferredLanguage($availableLocales) negotiates from the Accept-Language header, and App::setLocale($locale) applies the result. Wrap that in middleware so the locale is set on every request, persist an explicit user choice in the session or a profile column, and fall back to config('app.fallback_locale') when nothing matches.
- How do I switch locales in Laravel routes?
- Use route prefixing with a locale segment, for example Route::prefix('{locale}')->middleware('setlocale')->group(...), and constrain it with whereIn('locale', ['en', 'de', 'fr']). The middleware reads the route parameter, validates it against your supported locales, and calls App::setLocale(). URL generation then keeps the current locale automatically, which is the same route-based switching this bundle advertises.
- Does forci/locale-bundle support Laravel 10 or Laravel 11?
- No. Laravel version support is not applicable because the package targets Symfony's bundle system rather than Laravel's package discovery. Even if its PHP constraint happened to allow PHP 8.2 or 8.3, its Symfony framework-bundle constraints from the Symfony 3/4 era would conflict with what Laravel 10 and 11 require. There is also no maintainer signal, test matrix, or release cadence indicating Laravel support.
- Is forci/locale-bundle safe to use in production?
- The risk is high. The repository shows roughly 1 star and 0 dependents with a very low popularity score, no visible CI or test coverage, and no clear release cadence, so you should assume no upstream security response or bug fixes. Any adoption becomes a de facto fork that your team maintains. For a commodity feature, that is a poor supply-chain trade and will surface in dependency and procurement reviews.
- What license does forci/locale-bundle use?
- The detected license is NOASSERTION, which means no recognized OSI license was identified. That could be a custom or malformed license file, or no grant of rights at all. It is a legal blocker for commercial use and redistribution until counsel reviews the actual LICENSE file, so do not ship it before that question is answered.
- What are the alternatives to forci/locale-bundle for Laravel?
- Laravel's first-party localization already covers the core feature set: lang catalogs, __(), App::setLocale(), $request->getPreferredLanguage(), and locale-prefixed routes. If you want a community package specifically for URL-based locale routing, mcamara/laravel-localization is a widely used Laravel-native option. For translated content storage, pair the native catalogs with a Laravel translation package instead of a Symfony bundle.
- Is forci/locale-bundle a fork of another bundle, and is it actively maintained?
- It appears to be a Symfony 3/4-era bundle with minimal community traction and no visible release cadence, and it may be a fork or derivative of a better-known bundle such as LuneticsLocaleBundle. Check the repository history, the LICENSE file, and the composer.json constraints before relying on it. Given the abandonment risk, treat any use as a de facto fork that you own and maintain.
Weaver
How can I help you explore Laravel packages today?