-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[Refactor] use native JS instead of lodash #1419
Conversation
Using normal JS makes for far more understandable and maintainable code.
Using `.length` is clearer than a polymorphic `isEmpty`.
Going to go ahead and merge once tests all pass; the changes are minimal. The last commit also hopefully fixes the failing tests on master. |
Some eslint 3 tests still failing; I'll fix those and get tests passing on this PR prior to merging. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍🏼 though heads up, I also just pushed a fix to master to fix the no-deprecated tests, basically the same fix you have here
The test failures are pretty weird. No idea there. FWIW the webpack resolver still has a lodash reference, but it's declared in its |
This pr closes #1224 ? |
I can repro these failures locally - but when I check out latest master, they still fail :-/ |
This removes a large dep that often has CVEs, in exchange for using native JS which is clearer and more maintainable.
Closes #1224.