- How do I install Extended Laravel with Composer?
- Run composer require open-southeners/extended-laravel in a Laravel project. The README shows manual middleware registration for both the Laravel 10 Kernel.php style and the Laravel 11+ bootstrap/app.php style. The install docs contain a package-name typo, so confirm you are requiring extended-laravel and not laravel-helpers.
- Which Laravel versions does open-southeners/extended-laravel support?
- The package advertises broad support through Laravel 13 and PHP versions shown by its Packagist badge. Because it touches framework internals such as GeneratorCommand, verify the actual composer.json constraints and CI matrix against your Laravel version. Treat the broad claim as a compatibility target, not a guarantee.
- What helpers and mixins are included in Extended Laravel?
- It ships static helpers such as Helpers::modelFrom, instanceFrom, keyFrom, and queryFrom, plus facade mixins for Arr, Str, Number, Collection, Storage, and Config. Examples include Arr::exceptValues, Arr::onlyValues, Collection::toCsv, Collection::templateJoin, and Number::toShort. It also adds Eloquent casts, validation rules, global middleware, and Artisan commands.
- Does Extended Laravel override Laravel's make commands?
- Yes, it rebinds GeneratorCommand in the container so make:* commands route through its FileGeneratorCommand and OpensGeneratedFiles trait. That is not opt-in per call site; it changes framework behavior for the whole team. The changelog shows repeated fixes in this area, including four consecutive releases for the OpensGeneratedFiles namespace and a make:migration break fixed in 0.4.0.
- Is cache:clearLocks safe to run in production?
- cache:clearLocks deletes atomic locks, and the package docs carry their own warning about it. Running it against live workers can drop mutual exclusion and allow duplicate work. Treat it as a deliberate maintenance action and confirm whether your version supports scoping or pattern filtering before scheduling it.
- Can Extended Laravel's macros conflict with other Laravel packages?
- Yes, any package that macros Str, Arr, Number, Collection, or Config can silently overwrite another package's macro. The winner depends on service provider boot order. Test your full dependency set and avoid loading overlapping mixins in production.
- Why does the Extended Laravel documentation mention open-southeners/laravel-helpers?
- That is a documentation defect. The README overview and install section say composer require open-southeners/laravel-helpers, but the actual Composer package is open-southeners/extended-laravel. It is a sign the docs were not verified end to end, so double-check every install step.
- Does Extended Laravel use Laravel package auto-discovery?
- Auto-discovery and service-provider registration are not documented in the provided material. The docs show manual middleware registration only, which suggests partial manual wiring. Inspect composer.json for an extra.laravel providers entry and confirm which bindings the provider registers unconditionally.
- Is open-southeners/extended-laravel actively maintained?
- Adoption signals are essentially zero: no stars, no dependents, and a single agency-style maintainer. The last release is future-dated to 2026-08-12, which should be verified against tags and commits. The changelog also shows repeated regressions in the command override area.
- What should I use instead of Extended Laravel?
- Laravel's native Arr, Str, Collection, and Number helpers already cover many of these cases, and most teams keep the rest as internal support classes. Copying the specific snippets you need, such as Collection::toCsv or Number::toShort, avoids the GeneratorCommand override and macro collisions. If you need maintained macro packages, evaluate dedicated packages with active release cadence and tests against your Laravel version.