voidcosmos / voidcosmos/npkill
Invalid count value
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9.4k
- Forks
- 254
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
I just run npx npkill@latest --target .next on my Debian.
Initially it detects repos with .next, but theres label 1 error. 'e' to see and the Calculating stats still loading with static progress bar.
To Reproduce
Steps to reproduce the behavior:
- Open terminal and run
npx npkill@latest --target .next - See error
- When i click arrow up and arrow down, the error is increasing
2 error. 'e' to see=>3 error. 'e' to seeso on
Expected behavior
The npkill detects all .next without issues
Screenshots
- OS: Debian
- Version: v0.12.2
Additional context
Previously, I can use the same command to list all .next directories, but now it bugs
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing npx npkill@latest --target .next on Debian with version v0.12.2, then inspect the CLI entry point and the code responsible for calculating stats and handling arrow-key navigation. Done means .next directories are detected without the error count increasing, and the Calculating stats progress completes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100