Repository navigation
npx on windows - cannot find module with spaces in installation path #15095
Description
When I try to run npx --version on Windows where the installation path contains a space, the module cannot be found. This issue is not seen when Node is installed to a path containing no spaces.
- Version: 8.4.0
- Platform: Windows
Activity
Fishrock123 commentedon Aug 30, 2017
This should be reported to https://github.com/zkat/npx
TimothyGu commentedon Aug 30, 2017
I suspect this should probably be filed against the npx repo instead.
/cc @zkat
gibfahn commentedon Aug 31, 2017
Looks like zkat/npx#110
However I think it's worth having an issue here to note/track that the
npxthat comes with node is broken with the default windows install location (and the default shell).gibfahn commentedon Sep 5, 2017
@LuciusAterna not really possible, this happens when you run
npx, you don't specify the path to node.bzoz commentedon Sep 11, 2017
The issue here is not the Node.js path (it spawns just fine) but the
npm-cli.jspath containing spaces. This was fixed in zkat/npx@314e5eb, which is included in npm 5.4.0.gibfahn commentedon Sep 11, 2017
@nodejs/npm I know you guys are crazy busy, but an update to 5.4.0 (or even 5.4.1) would be really good, sounds like it has a bunch of new stuff!
bzoz commentedon Sep 13, 2017
Since #15347 got closed, maybe we should add a float patch zkat/npx@314e5eb, to make npx work?
gibfahn commentedon Sep 13, 2017
Depends how soon 5.4.2 is going to be out. I assume it'll be out pretty soon, in which case it probably makes more sense to just wait for that. This is a new feature that most people are unlikely to be relying on yet.
michaeljota commentedon Sep 15, 2017
Why no to update the npm version in latest yet? I was waiting for 8.5.0 to include this fix, but even when 5.4.x has been released before 8.5.0, it did not land there. Why?
(If it sounds rude, I did not mean it... I'm just curious)
zkat commentedon Sep 15, 2017
npm in node has included zkat/npx@314e5eb since 5.4.0. There's more issues here.
michaeljota commentedon Sep 15, 2017
Nope. npm as include the fix in 5.4.x and Node currently includes npm 5.3.0.
I just downloaded Node 8.5.0, got disappointed that it did not include the fix, and come here to comment.
michaeljota commentedon Sep 27, 2017
So... From comments in #15600 I can assume that the upgrade have not landed yet cause the stability of
npm@5.4.0, but seems likenpm@5.4.2is stable enough to land here before Node 8 goturboLTS...Lonsiege commentedon Nov 20, 2017
Looks like it is fixed in
npm@5.5.1michaeljota commentedon Nov 20, 2017
Not sure if it got fixed or this is the same error with different message
bzoz commentedon Apr 13, 2018
Fixed in #15600