7 ms·
As an aside, since it seems the other comments already address the core issue... No one should be using Lodash in 2025, it mutates your collections, use `ramda
by xx__yy 1y ago
As an aside, since it seems the other comments already address the core issue...
No one should be using Lodash in 2025, it mutates your collections, use `ramda` (https://ramdajs.com/ https://ramdajs.com/) instead.
Unfortunately, a lot of the early core existing packages have dependencies in lodash, or another packages that does so too.
- inbx0 1y agoEhh what. I would give some merit to arguments like "no one should use lodash in 2025 because you can do most of it with built-ins nowadays" or maybe because it doesn't tree-shake well or maybe even because it doesn't seem to have much active development now. But stating matter-of-factly that no one should use it because some of its well-documented functions are mutating ones and not functional-style, and should instead use one particular FP library out of the many out there, is not very cool.