[Suggestion] Drop lodash and replace to es-toolkit

[kms0219kms]

lodash is not actively maintained anymore, it hasn't been updated in ages.
For many functions, there are native JS alternatives nowadays and other more performant libraries.

Therefore, I am suggesting that replace lodash with es-toolkit, which is more modern, actively maintened (last update: 5 days ago), as well as incredibly fast (#).

This library supports drop-in replacement for lodash, so I personally think this is not too complicated task for this library.

FYI, Recharts and Storybook already use es-toolkit with same reason, so this library is well-tested and well-known now.

[snelsi]

Thanks for taking the time to share your suggestion.

We currently use lodash only for two functions: debounce and throttle. These implementations are stable, battle-tested, and have served us reliably for years. Given the limited and specific usage, there’s no tangible benefit to migrating to another library at this time.

We’ll stick with lodash for now to avoid unnecessary churn in the codebase.

Thanks for your input though!

[okinawaa]

Thank you for your thoughtful response. I completely understand your reasoning about stability and avoiding unnecessary churn. However, I'd like to respectfully present a few additional considerations that might change the cost-benefit analysis:

Bundle Impact for Users

Even with just 2 functions, the size difference is significant:

lodash: ~4KB (debounce + throttle)
es-toolkit: ~215 bytes (same functions)

That's a 95% reduction affecting all 800+ projects using react-resize-detector.

---

Zero-Risk Migration

The migration is literally a drop-in replacement

- import { debounce, throttle } from 'lodash';
+ import { debounce, throttle } from 'es-toolkit';

Same API, same behavior, zero breaking changes.

---

Maintenance Reality

While lodash's debounce/throttle are stable, the library itself hasn't seen meaningful updates in 2+ years. es-toolkit is actively maintained and already adopted by major projects like Storybook and Recharts for these exact reasons.

I understand if this still feels like unnecessary change, but given the minimal effort required and the collective benefit to your users, would you be open to reconsidering?

Thanks for maintaining such a useful library! 🙏

[maslianok]

This is the first time I’ve heard of “es-toolkit”. I spent 5 minutes reviewing their GitHub repo and documentation and everything looks solid: 8.2 k stars, active maintenance and clear docs.

That's a 95% reduction affecting all 800+ projects using react-resize-detector.

The size difference mentioned here is awesome!

@snelsi, shall we give it a try?

[kms0219kms]

@maslianok @snelsi We already opened the PR here: #266 and we also have codemod (https://github.com/toss/es-toolkit-codemod).

es-toolkit was developed by Viva Republica Inc., the creators of Toss, a popular financial app in Korea (#), and they have used this library extensively and tested it thoroughly. Since it is a financial app, they have conducted particularly rigorous tests for stability, so you can consider it sufficiently safe.