- What is andrey-helldar/laravel-support used for?
- It is a Composer package that provides reusable support classes and helper functions for Laravel and Lumen applications, focused on common tasks around arrays, strings, files, and similar utilities. It is intended to keep helper code clean, consistent, and easier to maintain across multiple projects. It is not a full application framework feature package; it is a utility layer you can share across Laravel codebases.
- How do I install andrey-helldar/laravel-support in a Laravel app?
- Install it with Composer using composer require andrey-helldar/laravel-support. Laravel package discovery normally handles service-provider registration for packages that ship one, so check bootstrap/cache/packages.php if helpers do not appear immediately. After installation, run your existing test suite to confirm the package resolves cleanly against your Laravel version.
- Does laravel-support support Laravel 13?
- Yes. Release 3.9.0 adds Laravel 13 compatibility, and the change is described as additive at the Composer constraint level. That means the package should resolve against Laravel 13 in addition to previously supported versions. The release notes do not state whether Laravel 13 support was validated by an expanded CI matrix or only by widening the constraint, so verify it in a branch before rolling it out broadly.
- Is version 3.9.0 a breaking change from 3.8?
- No new APIs, configuration surfaces, or extension points were introduced in 3.9.0. The functional change is Laravel 13 compatibility, with the rest of the release consisting of maintenance and housekeeping updates. It should be treated as a routine dependency refresh rather than a feature rollout, but still run your tests after upgrading.
- Do I need to publish config files or run migrations after installing laravel-support?
- No. The 3.9.0 release does not introduce or change published configuration or migration stubs. If your application already publishes package configuration from an earlier setup, keep it as-is; otherwise there is no publish or migrate step required for this release. Installation is primarily a Composer dependency update.
- Does laravel-support work with Lumen?
- The package is described as providing helper files for both Laravel and Lumen. Lumen does not use Laravel's package discovery in the same way, so if the package ships a service provider you may need to register it manually in bootstrap/app.php. After registration, confirm the helper functions or classes are available in a simple route or test.
- Will upgrading to 3.9.0 affect apps still on Laravel 11 or 12?
- For teams on Laravel 11 or 12, 3.9.0 is expected to be a no-op upgrade because the change is additive. The important check is whether the Composer constraint change narrowed the minimum supported Laravel version, which would be a silent breaking change for older projects. Bump the dependency in a branch, run composer update, and confirm it still installs on your current Laravel major before merging.
- How should I test laravel-support before using it in production?
- Upgrade the package in isolation on your current Laravel major first, then run your full test suite and any static analysis or smoke tests. Confirm the diff is limited to the Composer constraint, license, and image assets, since part of the 3.9.0 release is bot-authored housekeeping. Once that passes, schedule the same version as part of your Laravel 13 upgrade wave rather than treating it as an untested variable.
- Does laravel-support conflict with Laravel's built-in Arr and Str helpers?
- The package provides its own support classes and helper functions, so naming collisions are possible if it defines global helpers with the same names as Laravel's built-ins. In practice, Laravel's Arr and Str classes are namespaced, so class-based usage is less likely to conflict than globally defined functions. Check the package source or run a quick test if your application already defines custom helpers with similar names.
- Is andrey-helldar/laravel-support actively maintained, and what are the alternatives?
- The release history shows the package tracking Laravel's release cadence, with 3.9.0 adding Laravel 13 compatibility. The assessment notes that compatibility appears to be added reactively and that no per-major support or EOL policy is evident from the release notes, so confirm maintenance expectations with the maintainer if that matters to your team. Alternatives include Laravel's own Illuminate\Support helpers and smaller in-house utility packages, but replacing it means auditing every array, string, and file helper your services use.