build: remove lodash dependency and use native alternatives#1902
Merged
MarshallOfSound merged 1 commit intomainfrom Apr 8, 2026
Merged
build: remove lodash dependency and use native alternatives#1902MarshallOfSound merged 1 commit intomainfrom
MarshallOfSound merged 1 commit intomainfrom
Conversation
The only usage was _.get() in test/resedit.spec.ts for nested property assertions. Replaced with vitest's built-in toHaveProperty matcher, which supports the same dot-path notation.
dsanders11
approved these changes
Apr 8, 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
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.
Summarize your changes:
Removes the
lodashdependency and replaces its usage with native JavaScript alternatives. Specifically:_.get(rcOpts, key)withrcOptsand used Vitest'stoHaveProperty()matcher to assert both the property existence and valuelodashand@types/lodashfrom package.json dependenciesThis reduces the project's dependency footprint while maintaining the same test coverage and functionality. The native
toHaveProperty()matcher is more idiomatic for the testing framework being used.https://preview.claude.ai/code/session_01RP39NKFQFxTbxT8WBRakUB