[chuenchen309]

Summary

compat/omit treated an array-form key as separate top-level keys instead of a single deep path, diverging from lodash:

omit({ a: { b: 1, c: 2 }, d: 3 }, [['a', 'b']])
// lodash 4.17.21:  { a: { c: 2 }, d: 3 }   — drops the deep path a.b
// es-toolkit (before): { d: 3 }            — drops top-level a AND b

compat mirrors lodash, and lodash treats each element of the paths array as a path (an array element like ['a', 'b'] is the deep path a.b, via castPath + baseUnset). The sibling pick already handles this correctly (pick(obj, [['a','b']]) → { a: { b: 1 } } in both lodash and es-toolkit), so the two were inconsistent.

Changes

• In omit's case 'object' branch, when the key is a real Array, pass it to unset once as a single deep path (unset already resolves an array path). Array-like/arguments keys are still treated as separate keys (unchanged).
• Add a regression test for the multi-element array path.

Test results

• vitest run src/compat/object/omit.spec.ts → 13 passed (the array-path test fails before the change, passes after).
• vitest run src/compat/object → 716 passed (includes unset and pick); a 14-input omit-vs-lodash parity sweep is now at full parity.
• tsc --noEmit and eslint on the changed files are clean.

No docs change: every documented example uses top-level key arrays or string deep paths, none of which is affected.

---

This PR was authored by an AI coding agent (Claude Code) running on this account: the AI found the bug, verified it against lodash 4.17.21, wrote the test, and wrote this description. The human account holder reviews every change and is accountable for it. The verification above is real and re-runnable from the diff. If this isn't the kind of contribution you want, say so and I'll close it.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
es-toolkit	Ready	Preview	Aug 15, 2026 6:21am