Skip to content
New issue

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

#

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

Already on GitHub? # to your account

Jump to bottom

[BUG] the path resolution of npx is wrong when ancestor directory name include sign “&” #6376

Closed
2 tasks done
zihahahaha opened this issue Apr 19, 2023 · 2 comments
Closed
2 tasks done

[BUG] the path resolution of npx is wrong when ancestor directory name include sign “&” #6376

zihahahaha opened this issue Apr 19, 2023 · 2 comments
Labels
Bug thing that needs fixing Needs Triage needs review for next steps Release 9.x work is associated with a specific npm 9 release

Comments

@zihahahaha
Copy link

zihahahaha commented Apr 19, 2023 •
edited
Loading

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

on windows，if ancestor directory name include sign “&”，the path resolution will wrong when npx

Expected Behavior

it's easy to repair just replace SET dp0=%~dp0 width SET "dp0=%~dp0" in the batch script that npm generated

Environment

  • npm: 9.3.1
  • Node.js: 18.14.1
  • OS Name: windows
@zihahahaha zihahahaha added Bug thing that needs fixing Needs Triage needs review for next steps Release 9.x work is associated with a specific npm 9 release labels Apr 19, 2023
@Voltra
Copy link

Voltra commented May 3, 2023

Same here:

  • Node: 14.21.3
  • NPM: 9.6.5
  • OS: Windows 10 Pro (64 bits)

@milaninfy
Copy link
Contributor

Closing: this looks to be similar if not a duplicate of an existing issue,#7761. If you believe your instance is unique, please provide further clarifying details.

@milaninfy milaninfy closed this as not planned Won't fix, can't repro, duplicate, stale Aug 30, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
Bug thing that needs fixing Needs Triage needs review for next steps Release 9.x work is associated with a specific npm 9 release
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@zihahahaha @Voltra @milaninfy