Weave Code
Helpers Laravel Package
laravel/helpers
Backwards-compatibility package that restores Laravel 5.8 global helper functions for newer Laravel versions. Useful when upgrading legacy apps; helpers map to modern Arr and Str methods. Not accepting new helpers.
Provides backwards compatibility for helpers in the latest Laravel release.
Frequently asked questions about Helpers
- How do I install Laravel Helpers to maintain compatibility with Laravel 5.8 global helpers in Laravel 11+?
- Run `composer require laravel/helpers` in your project. The package automatically restores deprecated helpers like `array_get()`, `str_contains()`, and others globally, requiring no additional configuration. Ensure your Laravel version is between 6.0 and 12.x for compatibility.
- Will Laravel Helpers work with Laravel 12.x or is it only for older versions?
- Yes, Laravel Helpers explicitly supports Laravel 6.0–12.x as of v1.8.x. It’s designed as a temporary bridge for legacy codebases upgrading to newer Laravel versions. Check the [release notes](https://github.com/laravel/helpers/releases) for version-specific Laravel compatibility.
- Does this package add new helper functions, or does it only restore deprecated ones?
- This package **only restores** Laravel 5.8 global helpers (e.g., `data_get()`, `str_limit()`) that were removed or moved to `Arr`/`Str` classes. The Laravel team explicitly states **no new helpers** will be added—it’s a compatibility layer, not an extension.
- How do I migrate from Laravel Helpers to the modern Arr/Str methods (e.g., `Arr::get()` instead of `array_get()`)?
- Use static analysis tools like PHPStan or Psalm to identify deprecated helper usage. Replace calls incrementally (e.g., `array_get($array, 'key')` → `Arr::get($array, 'key')`). Laravel’s official docs provide [migration guides](https://laravel.com/docs/helpers#migration) for each helper.
- Can I use Laravel Helpers in a Laravel 5.x application, or is it only for upgrading?
- This package is **not for Laravel 5.x**—it’s designed to help **upgrade from 5.8 to newer versions (6.0–12.x)**. If you’re still on Laravel 5.x, focus on upgrading to Laravel 6+ first, then use this package as a temporary bridge during the transition.
- Will third-party packages (e.g., old Laravel plugins) break if I install Laravel Helpers?
- No, Laravel Helpers resolves ‘function not found’ errors in legacy vendor packages by restoring the missing global helpers. However, test thoroughly—some packages may still rely on removed Laravel 5.x behaviors not covered by this package.
- Is there a performance impact when using Laravel Helpers in production?
- Microbenchmarks show **negligible overhead (<0.5%)** for typical use cases. The package routes calls to the underlying `Arr`/`Str` classes, so performance is identical to native Laravel methods. No background processes or persistent storage are involved.
- What’s the long-term plan for Laravel Helpers? Will it be deprecated soon?
- The Laravel team plans to **deprecate and remove this package within 12–24 months**, aligning with Laravel’s migration to modern APIs. Use it as a temporary solution while refactoring legacy code. Monitor [Laravel’s upgrade guide](https://laravel.com/docs/upgrading) for official timelines.
- How do I test if Laravel Helpers is working correctly in my application?
- Verify by calling a restored helper (e.g., `array_get(['key' => 'value'], 'key')`) and checking the output matches Laravel 5.8 behavior. Run your existing test suite—if legacy helpers were working before, they should now. Use `php artisan optimize:clear` if helpers aren’t recognized.
- Are there alternatives to Laravel Helpers for maintaining backward compatibility?
- No official alternative exists. Other options include manually forking legacy packages or writing custom wrapper classes, but these lack the official support and seamless integration of Laravel Helpers. This package is the **recommended** solution for Laravel-specific legacy helper compatibility.
Weaver
How can I help you explore Laravel packages today?