This repository has been archived by the owner on Apr 22, 2023. It is now read-only.
The process.execPath does not return the absolute path of the node.exe in Windows #1341
Labels
Comments
|
I could not reproduce the bug. If I use the new official exe from nodejs.org, it displays full windows path in REPL:
|
|
Guys, can you post the output of |
|
windows 7 professional SP1 x64 - works |
|
Tried prebuilt 0.5.1: returns 'node' on WinXP SP3 (in VMWare) and on 32-bit Win7 no SP (standalone). Possibly unrelated but also failed to run CoffeeScript on both. |
|
Very strange. Prebuilt 0.5.1 returns full path on 64-bit Win7 SP1. I start node.exe and then enter process.execPath in REPL shell. |
|
Probably this was fixed in 48f65b3. Reopen if this is still an issue. |
|
I ran the exe on Windows XP SP 3 x86. FYI. |
richardlau
pushed a commit
to ibmruntimes/node
that referenced
this issue
Sep 18, 2015
Notable Changes: * build: Support for building io.js as a static library (Marat Abdullin) nodejs#1341 * deps: upgrade openssl to 1.0.2a (Shigeki Ohtsu) nodejs#1389 * npm: Upgrade npm to 2.8.3. (Forrest L Norvell) nodejs#1448 * src: allow multiple arguments to be passed to process.nextTick (Trevor Norris) nodejs#1077 * module: interaction of require('.') with NODE_PATH has been restored and deprecated. This functionality will be removed at a later point. (Roman Reiss) nodejs#1363
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Using the Windows
node.exe(v 0.5.1), when I typeprocess.execPath,"node"is returned, instead of the absolute path ofnode.exe, that is, where I placed it.BTW, thanks for releasing a windows version for node that does not require cygwin.
The text was updated successfully, but these errors were encountered: