fix(compat/omitBy): do not treat plain objects with numeric length as array-like

[raon0211]

Summary

Closes #1706

omitBy from es-toolkit/compat returned {} for any plain object that happened to have a numeric length property (e.g. Error instances, pg driver errors, winston info objects), because it treated array-likeness as authoritative. Lodash's _.omitBy does not — it operates on own enumerable keys regardless of length. This PR aligns the behavior with lodash.

Fixes the regression reported where omitBy({ level: 'error', message: 'hi', length: 104 }, isNil) returned {} instead of the original object, which also dropped symbol-keyed properties (e.g. winston's triple-beam routing key).

Changes

• Drop the isArrayLike branch in src/compat/object/omitBy.ts and unconditionally walk [...keysIn(object), ...getSymbolsIn(object)]. keysIn already handles real arrays correctly (returns indices as string keys), so the branch was unnecessary and actively wrong for plain objects with a numeric length.
• Remove now-unused range and isArrayLike imports.
• Add two regression tests in src/compat/object/omitBy.spec.ts:
  • plain object with numeric length is preserved when no value is nil
  • symbol-keyed properties survive on objects that also carry a numeric length

Test results

✓ src/compat/object/omitBy.spec.ts (11 tests) 3ms

Test Files  1 passed (1)
     Tests  11 passed (11)

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
es-toolkit	Ready	Preview, Comment	May 8, 2026 7:02am