- What does getsupercode/localizater actually do?
- Localizater is a single-purpose routing helper for Laravel. It lets one route definition fan out into locale-prefixed variants such as /en/pricing and /fr/pricing, and it provides locale-aware URL generation so controllers and Blade templates do not have to assemble locale prefixes by hand. A middleware reads the prefix and calls App::setLocale(). The package has no database, persistence, queue, or auth coupling, so it sits entirely in the routing and HTTP layer.
- Is getsupercode/localizater still maintained?
- No. The repository is archived with a single release in September 2020, a roughly 50-star footprint, and a composite score of 0.205. There is no security patching, no compatibility work, and no upstream maintainer to file a CVE with. Treat any upgrade question, such as whether it works on your next Laravel version, as work that lands on your own team.
- Does Localizater support Laravel 10, 11, or 12?
- Compatibility with Laravel 10, 11, or 12 and PHP 8.2 or 8.3 is unverified and almost certainly broken at the Composer constraint level. The package was built in the Laravel 6 to 8 and PHP 7.x era, so removed str_ and array_ helpers and Str class migrations are likely offenders. If your app is on Laravel 10 or newer, treat the code as source material rather than a runtime dependency.
- How do I install getsupercode/localizater?
- You would run composer require getsupercode/localizater, but expect constraint conflicts on modern Laravel versions. Before anything else, read the package composer.json require constraints and the service provider registration style to confirm which Laravel generation it targets. For Laravel 10 and above the practical answer is not to install it at all.
- Does Localizater work with route caching?
- Locale fan-out multiplies the registered route table, and a package that registers routes dynamically risks breaking route:cache and route:clear in ways that only surface in production. Verify the full cache cycle on a staging environment with your real locale set before relying on it. Low community exposure means these failure modes are unlikely to be well documented.
- How do I test Localizater before adopting it?
- Read composer.json require constraints and the service provider registration style first, then confirm the route macro registers after the router is booted. Test locale switching, locale-aware URL generation, and a full route:cache and route:clear cycle. Because the package is archived, plan to own any bug you find.
- Can I fork and vendor Localizater under packages/ instead?
- Forking and vendoring under packages/ is viable and takes an estimated two to four days, but it carries medium risk. It only makes sense if the package route macro semantics are already load-bearing elsewhere in your codebase. The work includes relaxing composer.json constraints, replacing removed str_ and array_ helpers with Str and Arr, and verifying macro registration timing.
- How do I add locale-prefixed routes in Laravel without a package?
- The native approach is roughly 150 lines: Route::group with a {locale} prefix, a small middleware that calls App::setLocale(), and a route() wrapper for locale-aware URLs. That covers most of the same ground as the package and is the preferred overall option because it has the smallest long-term liability and gives you full control. Estimate three to five days including tests and SEO plumbing.
- What are maintained alternatives to getsupercode/localizater?
- mcamara/laravel-localization is the maintained alternative and is the preferred choice if you want a third-party library, at an estimated three to five days of integration. If the team prefers zero third-party routing dependencies, reimplement in-house instead. Installing Localizater as a Composer dependency is rejected given the archived state and likely constraint conflict.
- Does Localizater handle hreflang and multilingual SEO?
- No. Localizater only covers locale-prefixed URLs; it does not handle hreflang, canonical tags, or crawlable alternates, so it is only half the localization story. You must implement those SEO concerns yourself in your layout or with a dedicated package. Decide your subdomain, query-string, or prefix strategy before adding any dependency.