When using the chocolatey nodejs.commandline package, it generates a shim in `C:\ProgramData\chocolatey\bin\node.exe`. After upgrading to the current version of node.js tools (1.0 RC2), it picked that path up as the default for node.exe. Unfortunately node.js tools seems to be doing a version check based on the exe version number. The node.exe shim has version number 0.2.2.0 (which points to node 0.10.35 on my machine). And I get an error message when trying to start the project: `This version of Node.js (0.2.2.0) is not supported. Please upgrade to Node.js v0.10.20 or later.`
If I set my node.js path to the actual node.exe all is well. But that encodes an explicit version from chocolatey which I'd rather avoid: `C:\ProgramData\chocolatey\lib\nodejs.commandline.0.10.35\tools\node.exe`
Options to fix:
1. Somehow detect the shim and figure out where it points to.
2. Config option to skip the version check against the exe.
3. Better detection of where node.exe really is.
4. Something smarter than I can think of!
Murray
If I set my node.js path to the actual node.exe all is well. But that encodes an explicit version from chocolatey which I'd rather avoid: `C:\ProgramData\chocolatey\lib\nodejs.commandline.0.10.35\tools\node.exe`
Options to fix:
1. Somehow detect the shim and figure out where it points to.
2. Config option to skip the version check against the exe.
3. Better detection of where node.exe really is.
4. Something smarter than I can think of!
Murray