- What is approached/laravel-date-international used for?
- It is a small Laravel package for locale-aware date formatting, intended to transform date strings so they read naturally for users in different languages and regions. It fits presentation-layer use cases such as Blade views, exports, forms, and admin screens.
- Is laravel-date-international compatible with Laravel 10 and Laravel 11?
- The repository does not document support for Laravel 10 or 11, and the package was last released in 2020 and is archived. Its illuminate/* and Carbon constraints may conflict with modern Laravel versions, so run a compatibility spike and composer why-not before adopting.
- How do I install laravel-date-international with Composer?
- Install it with Composer using composer require approached/laravel-date-international, then confirm that Laravel package discovery registers the service provider and any facade. Because the package is archived, test the install in a disposable branch against your exact Laravel, PHP, and Carbon versions.
- Does this package use Carbon or PHP IntlDateFormatter for locale formatting?
- The available context says it integrates with Carbon and Blade, but it does not confirm whether it also relies on IntlDateFormatter or custom translation files. Inspect the source and composer.json to see the exact dependencies before relying on it.
- Which locales and date formats does laravel-date-international support?
- The package is described as a date string transformator for your language, but the provided overview does not list supported locales or patterns. Verify the locales you actually ship and test fallback behavior for missing locales.
- How does the package handle timezones and daylight saving time?
- The package is a presentation-layer date formatter and the context does not document its timezone or DST handling. Test formatted output under your application timezone and around DST boundaries, and validate invalid or ambiguous input.
- Can I use laravel-date-international in Blade templates?
- Yes, Blade integration is part of the package's stated purpose, so it can be used to render localized dates in views. Still wrap calls in an internal adapter or Blade directive so you can replace the package without touching templates.
- Is laravel-date-international maintained and safe for production?
- It is not actively maintained: the last release was in 2020 and the repository is archived, so it receives no upstream fixes, security patches, or Laravel compatibility work. Treat it as a low-blast-radius utility, pin the version, wrap it, and assign an owner for replacement.
- What should I do if the package is abandoned or incompatible with my Laravel version?
- If it is incompatible, fork it under a private namespace if MIT licensing and ownership cost are acceptable, or replace it with an internal formatter built on Carbon and IntlDateFormatter. An internal adapter such as App\Support\LocalizedDateFormatter keeps that migration invisible to product code.
- What are alternatives to laravel-date-international for localized dates in Laravel?
- Prefer a thin internal date-formatting service built on Carbon and PHP IntlDateFormatter, optionally combined with Laravel translation files. This avoids lifecycle risk and gives you deterministic locale behavior and control over fallbacks.