voidcosmos / voidcosmos/npkill
npkill doesnt show node_modules in nested routes
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 have a webs folder
inside webs folder i have ALL my projects with react, some not with react, etc
node_modules
so i run "npx npkill" under my webs directory: C:\Users\jesu\documents\webs> npx npkill
what happens, doesnt list me anything
just that
inside webs folder, this first 3 folders have node_modules inside
but npkill doesnt care and dont list me anything
i have like 50 more folders to scan
what can i do here, i tried npx npkill -f, npx npkill -d ./webs
nothing seems to work
its just:
webs/web1/node...
webs/web2/node...
and that. i dont have npm workspaces
but npkill doesnt care
To Reproduce
Steps to reproduce the behavior:
npx npkill
i tried with git bash, cmd, powershell, vscode, all under administrator privileges
this only seems to happen to me
Expected behavior
i expect to list my node_modules, then delete all, just that, Keep It Simple S....
Screenshots
i dont have screenshot
last node version
las windows updates (22h2)
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 the scan from the webs directory with nested projects, including the reported npx npkill and -d ./webs commands. Inspect the directory traversal entry point and verify that nested node_modules directories are listed and can be selected for deletion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100