-
-
Notifications
You must be signed in to change notification settings - Fork 10.7k
refactor(dev): migrate lodash
to es-toolkit
and add type-safety to ConfigPreset
#14111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Hi @cksal0805, Welcome, and thank you for contributing to React Router! Before we consider your pull request, we ask that you sign our Contributor License Agreement (CLA). We require this only once. You may review the CLA and sign it by adding your name to contributors.yml. Once the CLA is signed, the If you have already signed the CLA and received this response in error, or if you have any questions, please contact us at [email protected]. Thanks! - The Remix team |
Thank you for signing the Contributor License Agreement. Let's get this merged! 🥳 |
2883209
to
1929d95
Compare
I must be missing something, but this looks like it increases the size of the package? Here's my build steps: pnpm clean
pnpm i
pnpm build
cd packages/react-router-dev
pnpm pack
ls -l react-router-dev-7.7.1.tgz I did those on the SHA prior to this branch and the HEAD of this branch:
|
Aren't we only using the utils we import from
|
lodash
to es-toolkit
and add type-safety to ConfigPreset
Closing because as noted in #14180 (comment) |
If you're going to AI slop something, at-least spend some time making sure the description is correct. Not sure where the other 42 file changes are. |
Summary
TL;DR
This PR proposes replacing
lodash
withes-toolkit
across the codebase.lodash
imports in ~48 files withes-toolkit/compat
equivalentsWhy this change might help:
All tests pass, and core functionality works as expected.
This is a suggestion for consideration — open to feedback or rollback if needed.
https://es-toolkit.dev/compatibility.html
Thanks