fix: stack overflow when scanning large number of JSONL (SUPER TINY PR +1-1) #17
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.
Summary
~/.claude/projectsProblem
Users with many JSONL files (100k+) see "No usage history found" even though files exist.
Root cause:
allFiles.push(...files)causes "Maximum call stack size exceeded" when the array has more than ~65,536 elements. The catch block silently swallows this error, making it appear as if no files were found.Solution
Replace the spread operator with a for loop: