[jidohyun]

This PR improve the orderBy, sortBy function, as requested in the issue(#869)

Added:

• sortBy and orderBy string array support: Enhanced both functions to work with primitive arrays (strings, numbers, etc.) by removing T extends object constraint
• Optional criteria parameters: Made criteria parameter optional with default empty array, enabling direct primitive sorting without explicit functions
• Optional orders parameter: Added default ascending order to orderBy for simplified usage
• Comprehensive test cases: Added tests for string arrays, number arrays, empty criteria, and mixed sorting scenarios using consistent ['apple', 'banana', 'cherry'] pattern
• Enhanced documentation: Updated JSDoc with primitive array examples and usage patterns for both Korean and English docs
• Type safety improvements: Maintained full type inference while supporting broader input types
• Backward compatibility: Preserved all existing object sorting functionality without breaking changes

Here is the screenshot of the performance benchmark results:

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
es-toolkit	Ready	Preview	Comment	Dec 9, 2025 5:16am

[raon0211]

Thank you for the PR!

However, for arrays of strings or other primitives, I think using the native sort directly is much more natural and better ergonomics:

arr.sort((x, y) => x.localeCompare(y));

sortBy and orderBy are designed for sorting arrays of objects by their properties, and extending them to primitives adds complexity to the API without a clear benefit over what modern JavaScript already provides. This also aligns with our design principle of not implementing features that are easily replaceable by modern JS.

So I'll close this PR. Thanks again for your contribution and interest in es-toolkit!