Skip to content
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

[BUG] While running npm commands, it doesn't show current directory where I am in after the command finish executing #7318

Closed
2 tasks done
nitin065 opened this issue Mar 27, 2024 · 5 comments
Labels
Bug thing that needs fixing Needs Triage needs review for next steps Release 10.x

Comments

@nitin065
Copy link

nitin065 commented Mar 27, 2024

Is there an existing issue for this?

  • I have searched the existing issues

This issue exists in the latest npm version

  • I am using the latest npm

Current Behavior

After running any command, after it finishes, it does not show up currect directory I am in, making it look like it is still running the command. Here below, I ran first npm version command, then few other commands all marked with red underline. It just shows a blinking icon.
npmCapture

Expected Behavior

Command should not remove showing my current directory.

Steps To Reproduce

  1. In Windows environment
  2. With this latest npm version
  3. Run 'npm version' or any npm command
  4. See that the command doesnot show my current directory

Environment

  • npm: 10.5.0
  • Node.js: 20.5.1
  • OS Name: Windows 10
  • System Model Name:
  • npm config:
; Check the attached image
@nitin065 nitin065 added Bug thing that needs fixing Needs Triage needs review for next steps Release 10.x labels Mar 27, 2024
@milaninfy
Copy link

@nitin065 I tried reproducing this issue on windows cmd, but it works as expected. This might have something to do with command prompt setting, You can try updating npm to latest version or clean reinstall of node and npm and check if that fixes this issue. Also, have you tried running it on different terminal program like PowerShell or Bash to see if it happens on them as well ?

@nitin065
Copy link
Author

I tried on PowerShell, there I don't see the problem.
I tried with CMDER. There too I am seeing same problem.

I am using latest version of node and I don't have any special settings.

@milaninfy
Copy link

@nitin065 If it works well on windows powershell and windows command prompt then it's not and issue with npm.

@nitin065
Copy link
Author

@milaninfy, in windows command prompt it is not working. CMDER is also a tool where it does not work.
I tried in Windows terminal too, where I selected Windows CMD, it don't work there.

Not Working in Tools:

  • Windows CMD
  • Windows Teminal
  • CMDER

Working:

  • PowerShell

@wraithgar
Copy link
Member

This does not seem like an npm problem, but your local windows terminal setup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug thing that needs fixing Needs Triage needs review for next steps Release 10.x
Projects
None yet
Development

No branches or pull requests

3 participants