Skip to content

/ npkill

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

npkill lists home directory #40

Open
haykam821 opened this issue Aug 27, 2019 · 3 comments
Open

npkill lists home directory #40

haykam821 opened this issue Aug 27, 2019 · 3 comments
Labels
bug good first issue help wanted

Comments

@haykam821
Copy link

@haykam821 haykam821 commented Aug 27, 2019

Description

npkill lists the home directory as a node_modules directory:

npkill showing home directory

Reproduction

  1. Run npkill --sort size.
  2. Wait for search to complete.
  3. Do other tasks, and return to the process.
  4. /Users/user/. will appear on the list.

I was able to reproduce this multiple times.

Expected Behavior

I expected for the home directory to not be listed.

Additional Information

I am using macOS Mojave 10.14, with npkill version 0.5.0, npm version 6.10.2, and node version 12.8.1.
@zaldih zaldih added the bug label Aug 27, 2019
@zaldih
Copy link
Member

@zaldih zaldih commented Aug 27, 2019

Hi there! Thanks for reporting this bug and for the details.
Could you check if this same error happens in previous versions? Trying for example:
npx npkill@0.4.0 or npx npkill@0.3.0
@LegalOwl
Copy link

@LegalOwl LegalOwl commented Oct 14, 2020

Hi there,

so far I was unable to reproduce this issue on macOS Catalina 10.15.7 with the last version of npkill (0.7.2). Could you please verify if you can still reproduce this issue in the latest version and if you can produce it all the time or if it just occurs occasionally?
@PDavid
Copy link

@PDavid PDavid commented Oct 18, 2020

Hi All,

I was able to reproduce this issue on Ubuntu 20.04 LTS with npkill v0.7.2.

image

I tried this several times with the latest version and the issue occurs every time.

Also tried but cannot reproduce the issue with 0.3.0 or 0.4.0,
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug good first issue help wanted
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
@PDavid @zaldih @haykam821 @LegalOwl
You can’t perform that action at this time.