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.

Sign up for GitHub

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

[BUG] "npm explore <pkg>" fails on Windows (node.js LTS) #554

Closed
flash-me opened this issue Dec 4, 2019 · 2 comments
Closed

[BUG] "npm explore <pkg>" fails on Windows (node.js LTS) #554

flash-me opened this issue Dec 4, 2019 · 2 comments
Labels
Bug thing that needs fixing platform:windows is Windows-specific

Comments

@flash-me
Copy link

flash-me commented Dec 4, 2019

What / Why

Windows 10 | Node.js LTS (12.13.1) | npm 6.13.2

Running npm explore <pkg> fails no matter which name is provided for <pkg>

How

Current Behavior

image

Steps to Reproduce

  1. Install node.js
  2. Install any global
  3. npm explore <package>

Expected Behavior

npm explore <package> must not fail

Code Location

I put some logs in npm-cli & explore & escape-exec-path.
The error is thrown @ path.normalize(str) where str=undefined
Here is the output:
image
@flash-me
Copy link
Author

flash-me commented Dec 4, 2019 •
edited
Loading

Ok, just had a look into this change 6cc4cc6
Seems that it does not fix the issues as expected.. Reverting does not fix it neither.

It gets funny quite fast when starting to dig in. Issues on windows with whitespaces in paths. Which kind of terminal to call, bash or cmd prompt?...

flash-me referenced this issue Dec 4, 2019
@isaacs
explore: escape args properly on Windows Bash
6cc4cc6 
Despite being bash, Node.js running on windows git mingw bash still
executes child processes using cmd.exe.  As a result, arguments in this
environment need to be escaped in the style of cmd.exe, not bash.
@darcyclarke darcyclarke added platform:windows is Windows-specific Bug thing that needs fixing labels Oct 30, 2020
@darcyclarke
Copy link
Contributor

npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.

If your bug is preproducible on v7, please re-file this issue using our new issue template.

If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo

Closing: This is an automated message.

This was referenced Oct 21, 2024
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug thing that needs fixing platform:windows is Windows-specific
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@darcyclarke @flash-me