migrate
Lodash Migration & Compat Guide
Guide users through migrating lodash to es-toolkit and understanding the strict vs compat APIs, grounded in actual source code.
Input
$ARGUMENTS — Lodash code to migrate, specific function names, or a question about strict vs compat.
Core Concepts
es-toolkit (strict): Opinionated, simplified API for the 85% use case. Smaller bundle, may differ from lodash in edge cases by design. New functions are added here.
es-toolkit/compat: Aims for full lodash test compatibility within a defined scope. See docs/compatibility.md for out-of-scope behaviors (e.g., implicit type conversions, prototype modifications).
Why source-first matters
The only reliable way to know the difference between strict and compat is to read the actual implementation. Never guess — always verify from source.
Workflow
More from toss/es-toolkit
recommend
Analyze code or requirements and recommend the best es-toolkit functions. Use when the user asks which es-toolkit function to use, needs help finding a utility, or wants alternatives to manual implementations.
132guide
es-toolkit usage guide covering installation, import patterns, and setup for Node.js, Bun, Deno, and browsers. Use when the user asks how to install, import, or set up es-toolkit in their project.
103compat-review
Verify compat PR claims by running lodash vs es-toolkit/compat at runtime
44pr-triage
Classify and summarize a PR for efficient review
38pr-review
Review recent PRs with deep context and label-specific checks
38release
Create a new es-toolkit release (version bump, changelog, tag)
37