remove lodash#12
Open
honey32 wants to merge 2 commits into
Open
Conversation
honey32
force-pushed
the
26-0517-remove-lodash
branch
from
May 23, 2026 05:41
e552e3e to
a3d69f4
Compare
imcuttle
approved these changes
May 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I really like this package. But I found something to improve in this package.
lodashtransitive dependency sometimes become a little bit burden for us (end-user app devs) because lodash sometimes reported as vulnerable.That kind of situation is becoming more often thanks to active diagnostics using AI or due to frequently happening supply-chain attacks.
So I believe that removing lodash from deps will keep this package resilient against supply-chain attacks and (close to) maintenance free.
Inspired by: https://e18e.dev/learn/cleanup.html