"Path must be a string. Received undefined"

[UTGuy]

• npm v5.51
• node v8.9.0

... it seems that anytime I run an npx command it shows "Path must be a string. Received undefined"

[only-cliches]

Also getting this error, it seems like npx isn't able to scan and find already installed packages.

• Windows 10
• npm 5.5.1
• node 8.9.3

[styfle]

I get the same error on Windows 10.

C:\Users\styfle>node --version
v8.9.4

C:\Users\styfle>npm --version
5.6.0

C:\Users\styfle>npx --version
npx: installed 1 in 2.147s
Path must be a string. Received undefined
9.7.1

[laggingreflex]

Dupe #148

[denishowe]

npx.cmd does
CALL "%NODE_EXE%" "%NPX_CLI_JS%" prefix -g
which is
node c:/nodejs/node_modules/npm/bin/npx-cli.js prefix -g
when it looks like it should be doing
npm prefix -g
Where exactly does npx.cmd come from?

[laggingreflex]

This PR should fix it

[bluelovers]

The "path" argument must be of type string

[oshingc]

I have this issue...

[Sawtaytoes]

@laggingreflex Looks like the PR failed when run through the CI tool.

[colwilson-mo]

Windows 10

node -v
v8.9.4

npm -v
5.6.0

npx -v
npx: installed 1 in 2.458s
Path must be a string. Received undefined
9.7.1

[rmx90210]

Same issue here.

Windows 7
Node 8.9.4
npm 5.6.0
npx 9.7.1

[Darkle]

I'm getting this as well.

Windows 10
Node v8.10.0
npm 5.7.1
npx 9.7.1

[eybbus]

Same issue here.

Windows 10 64 bit
Node 8.9.4
npm 5.6.0
npx 9.7.1