microsoft / nodejstools

Node.js Tools for Visual Studio
http://aka.ms/explorentvs
Apache License 2.0
1.79k stars 359 forks source link

SELECT Node version #1920

Closed jmaFinistereVar closed 6 years ago

jmaFinistereVar commented 6 years ago

Hello,

I am using Visual 2017 for my typescript developments. I have two versions of Node installed on my PC:

I try to swtich from one to the other through "Option / Tools / Web Package Management" but even when I select folder "C:\Program Files\nodejs_V8\node-v8.9.3-win-x64" at the top of the list it is always Node V4 that is running. I would like to know how I can select Node v8 ?

Note: this question has also been asked on Microsoft forum

paulvanbrenk commented 6 years ago

Sorry about the terrible response on the Microsoft Forum... at least it got you here.

For the Node Tools, you can select the node version you use in Project Properties, if you don't want to use the one defined in your path. (Currently we don't look at the version specified in "Option / Tools / Web Package Management").

image

jmaFinistereVar commented 6 years ago

Thank you very much for your answer. I updated the node version but I ran into a new probem : when trying to install sqlite3 with the options --build-from-source --scripts-prepend-node-path="C:\\Program Files\\nodejs_V8\\node-v8.9.3-win-x64\\node.exe" it failed with the message

npm WARN invalid config scripts-prepend-node-path="C:\\Program Files\\nodejs_V8\\node-v8.9.3-win-x64\\node.exe" sqlite3@4.0.0 install C:\Users\jerome.marquet\Documents\workSpace\services\isogeo-sdk-ts\NodejsConsoleApp1\node_modules\sqlite3 npm WARN lifecycle npm is using C:\Program Files\nodejs_V8\node-v8.9.3-win-x64\node.exe but there is no node binary in the current PATH. Use the --scripts-prepend-node-path option to include the path for the node binary npm was executed with. node-pre-gyp install --fallback-to-build 'node' n'est pas reconnu en tant que commande interne ou externe, un programme executable ou un fichier de commandes.

So my ew question is do you know how to use the --scripts-prepend-node-path option ? Or is it broken on Visual 2017 ?

Best regards image

jmaFinistereVar commented 6 years ago

Sorry,I understood my problem. The correct option is --build-from-source --scripts-prepend-node-path not --build-from-source --scripts-prepend-node-path="xx/yy/zz"

paulvanbrenk commented 6 years ago

@jmaFinistereVar glad you figured it out.