Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Laravel Lodash

Laravel Lodash Laravel Package

longman/laravel-lodash

Laravel Lodash brings Lodash-inspired helpers to Laravel and PHP for arrays, objects, and strings: get, set, has, pick, omit, camelCase, and more. A fluent lodash() helper keeps common data manipulation short, chainable, and readable.

View on GitHub
Deep Wiki
Context7

Laravel Lodash integrates the lodash-php utility library into Laravel, giving you expressive Lodash-style helpers for arrays, collections, strings, objects, and numbers. It fits naturally into Laravel apps via a service provider and facade, keeping common data transformations concise and readable.

  • Auto-discovered Laravel service provider and Lodash facade
  • Global helper for quick Lodash calls
  • Chainable array, collection, and string utilities
  • Consistent Lodash-style API across your app
  • Works alongside native Laravel collections
Frequently asked questions about Laravel Lodash
What is longman/laravel-lodash and what does it add to Laravel?
longman/laravel-lodash is a small Laravel utility package that brings Lodash-style helpers to PHP. It adds global functions such as _get, _set, _has, _unset, _pick, and _omit for working with arrays and objects using dot-notation paths. It is an additive helper layer rather than a persistence, queue, or HTTP package. Treat it as a convenience dependency, not a core abstraction.
How do I install longman/laravel-lodash in a Laravel app?
Install it with Composer using composer require longman/laravel-lodash. In a typical Laravel application, package auto-discovery registers the service provider, and no configuration file or migration is required. Verify the exact install steps against the package README or Packagist page because the supplied material does not include primary documentation. After install, confirm the helper functions are available in your target environment.
Which Laravel and PHP versions does longman/laravel-lodash support?
The supplied material does not confirm a supported Laravel or PHP version matrix. Before adopting it, check Packagist, the README, and any CI configuration for explicit Laravel 10, 11, and 12 plus PHP 8.1 through 8.4 coverage. If the package does not publish a matrix, test it against your exact Laravel and PHP versions. Do not assume compatibility from the package name alone.
What does longman/laravel-lodash add that Laravel Arr and Collection helpers do not?
The package is described as a thin layer of Lodash-style convenience helpers for arrays and objects, especially dot-notation access and manipulation. Laravel core already provides helpers such as Arr::get, Arr::set, Arr::has, Arr::forget, data_get, and Collection methods, so overlap is likely. Ask for or build a concrete function inventory and compare it with Illuminate\Support\Arr, Str, Number, and Collection on your target Laravel version. Adopt it only where the delta is clear and useful.
Do the helpers in longman/laravel-lodash support dot notation for nested arrays?
Yes. The package description says _get, _set, _has, _unset, _pick, and _omit work with arrays and objects using dot-notation paths. That makes it similar in intent to Lodash's get and set helpers in JavaScript. Because edge-case behavior is not documented in the supplied material, test nulls, missing keys, empty arrays, numeric keys, and unicode values in your own suite.
Does longman/laravel-lodash register global functions, macros, or both?
The overview describes global functions such as _get and _set, which is the highest-collision-risk integration pattern. The supplied material does not confirm whether the package also registers macros on Laravel core classes. Check the service provider source to see exactly what is registered and whether any existing Collection or Arr method names are shadowed. Global helper names should be audited against your application and dependencies before rollout.
Is longman/laravel-lodash safe to use in production?
It has a small architectural footprint because it adds helpers rather than persistence, queues, or external services. The main risks are lifecycle and supply chain: the material notes a single maintainer, zero dependents, no package documentation in the supplied bundle, and unverified release metadata. It should not sit in a critical path or become a load-bearing abstraction. If you adopt it, pin the version, vendor or fork it if needed, and keep a removal plan.
How should I test code that uses longman/laravel-lodash helpers?
Pin the package version and write focused PHPUnit or Pest tests around every helper you use. Cover empty arrays, null values, missing dot-notation paths, numeric keys, unicode strings, and overwrite behavior for _set. Also test the exact Laravel version you deploy, because future Laravel releases may add similarly named helpers. If the package has no published test matrix, your own tests are the compatibility contract.
What are alternatives to longman/laravel-lodash for dot-notation array access?
Laravel's built-in Arr::get, Arr::set, Arr::has, Arr::forget, data_get, and Collection methods cover many dot-notation use cases without an extra dependency. You can also add a small internal helper file if you need only a few Lodash-style functions. Staying with core helpers reduces collision and maintenance risk. Compare the package's function inventory with Laravel core before adding another dependency.
What should I check before adding longman/laravel-lodash to an existing Laravel codebase?
Confirm the actual supported Laravel and PHP versions, the full helper inventory, and whether it registers global functions, macros, or both. Audit name collisions with your own helpers and with future Laravel core methods. Decide where helpers are allowed, such as presentation or formatting code rather than domain logic. Verify Packagist release history and pin a known version before piloting it.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
robertmarney/lara-hierarchial-collections
simonschaufi/rule-doc-generator
emissaoja/emissaoja
blackbricksoftware/gravityforms-civicrm-form-processor
al-rahabi/fancy-crud
jinas/dhivatar-component
mltstephane/laravel-quality
bernskiold/laravel-talentlms
bernskioldmedia/laravel-form-architect
youbar/easy-crud
c-point-labs/laravel-hostyourai
dbravoan/dbcms-admin-theme-dbcms
dbravoan/dbcms-theme-db-cyber
dbravoan/dbcms-blocks-basic
dbravoan/dbcms-module-content-audit
dbravoan/dbcms-module-ai-assistant
paygate-to/paygate-php
padosoft/askmydocs-connector-base
defstudio/supercharged-carbon
bernskioldmedia/laravel-matomo