You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After run command npx depcheck . in project with about 900 files it just hung.
It continues to create a load on the CPU, but after 50 minutes of waiting I concluded that this is not expected behavior
I didn't find any verbose flags or anything like that.
& time npx depcheck .
^C
> npx depcheck . 4112.94s user 1209.58s system 162% cpu 54:35.66 total
As it turned out, the reason for this behavior is that the crawler left the project directory following symlinks and went to index half of my operating system XD.
Context:
We use devbox that create .devbox dir in project, and provide virtual environment for project (node, java, go, docker etc.).
I ran depcheck with the . --ignore-path=.gitignore parameter, assuming that this folder would be ignored, but I forgot that this folder is ignored by git because it has .gitignore inside it. (another way to ignore dirs).
In fact, there are tons of ways to ignore folders,
and it may be difficult to list them all manually to pass them to a --ignore-path parameter.
Possible solution:
I think a good solution would be to ask the git directly which files to ignore. Something like depcheck --ignore-gitignored, and when it enabled depcheck uses command git ls-files --others to determine what doesn't need to be checked
Bug Description
After run command
npx depcheck .
in project with about 900 files it just hung.It continues to create a load on the CPU, but after 50 minutes of waiting I concluded that this is not expected behavior
I didn't find any verbose flags or anything like that.
Steps
https://github.com/konturio/disaster-ninja-fe
npx depcheck .
Actually I noticed that even to show the version or
--help
it takes the utility as much as 3.77sVersions
node -v
: v20.8.0npm -v
: 10.1.0depcheck --version
: 1.4.7Extra info
The problem is definitely not in the hardware.
The text was updated successfully, but these errors were encountered: