Moving from lodash to es-toolkit

es-toolkit is best understood as a modern option for projects built around ESM, TypeScript, and tree-shaking—not as a moral replacement for lodash.

Evaluate the move in the context of your actual bundle, imports, browser targets, types, and performance-sensitive code. The benefit of a smaller or more tree-shakeable utility layer disappears if a migration introduces subtle behavioral changes or leaves mixed patterns everywhere.

A compatibility layer can make migration incremental. Replace well-understood imports first, verify behavior with tests, inspect the production bundle, and keep the choice reversible. The goal is a cleaner, more maintainable utility boundary, not a dependency swap for its own sake.