npx on windows - cannot find module with spaces in installation path

[BethGriggs]

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

(https://nodejs.org/dist/v8.4.0/node-v8.4.0-x64.msi)

[Fishrock123]

This should be reported to https://github.com/zkat/npx

[TimothyGu]

I suspect this should probably be filed against the npx repo instead.

/cc @zkat

[gibfahn]

Looks like zkat/npx#110

However I think it's worth having an issue here to note/track that the npx that comes with node is broken with the default windows install location (and the default shell).

[gibfahn]

Try enclosing the whole path with double quote.

@LuciusAterna not really possible, this happens when you run npx, you don't specify the path to node.

[bzoz]

The issue here is not the Node.js path (it spawns just fine) but the npm-cli.js path containing spaces. This was fixed in zkat/npx@314e5eb, which is included in npm 5.4.0.

[gibfahn]

@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]

Since #15347 got closed, maybe we should add a float patch zkat/npx@314e5eb, to make npx work?

[gibfahn]

Since #15347 got closed, maybe we should add a float patch zkat/npx@314e5eb, to make npx work?

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]

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]

npm in node has included zkat/npx@314e5eb since 5.4.0. There's more issues here.

[michaeljota]

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]

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 like npm@5.4.2 is stable enough to land here before Node 8 go turbo LTS...

[Lonsiege]

Looks like it is fixed in npm@5.5.1

[michaeljota]

Not sure if it got fixed or this is the same error with different message

[bzoz]

Fixed in #15600