Repository navigation
fix: don't count modules inside found directories twice in search total - #743
Conversation
🦋 Changeset detectedLatest commit: cb1d322 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
Walkthrough
Priority: ⬇️ Low Severity of issue fixed: Low Merge Risk: ⚪ Minimal · up to
|
|
Could you sign the CLA? |
|
Signed |
valscion
left a comment
There was a problem hiding this comment.
Thanks, looks good to me!
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #743 +/- ##
==========================================
- Coverage 89.92% 87.49% -2.44%
==========================================
Files 17 20 +3
Lines 1132 1271 +139
Branches 420 444 +24
==========================================
+ Hits 1018 1112 +94
- Misses 105 146 +41
- Partials 9 13 +4 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Fixes #251
foundModulesSizesummed every match, so when a directory and modules inside it both matched (e.g. searchinglodash), the modules were counted once in the directory's size and again on their own. It now walks the tree and stops at the first found node, as suggested in #251 (comment).Added
test/store.jscovering directory, module and mixed matches (fails on main with 60 instead of 30).npm testandnpm run lintpass.Written with help from an AI coding assistant.
Summary by CodeRabbit