search

jens1101 / SteamCMD-JS-Interface

Allows you to access and use SteamCMD via JavaScript
14 stars 2 forks source link

Module won't install getting python error #8

Closed Killa4 closed 4 years ago

Killa4 commented 4 years ago

Not really sure whats going on. Tried install, reinstall the node_gyp got nothing. Tried updating node got nothing. Tried install python itself and still getting the same error

https://gyazo.com/f5707270882008a970448f4ff06c1469

jens1101 commented 4 years ago

Node-pty, one of the dependencies, has native extensions. So it has to compile some C++ code while you run npm install. I got this to work on my Windows machine by running the following: npm install --global --production windows-build-tools and then installing steamcmd-interface. You can find more information here: https://www.npmjs.com/package/node-pty?activeTab=readme#windows

Let me know if this works for you.

Killa4 commented 4 years ago

I seem to be having issues still

gyp ERR! find VS gyp ERR! find VS msvs_version not set from command line or npm config gyp ERR! find VS VCINSTALLDIR not set, not running in VS Command Prompt gyp ERR! find VS checking VS2017 (15.9.28307.280) found at: gyp ERR! find VS "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community" gyp ERR! find VS - "Visual Studio C++ core features" missing gyp ERR! find VS checking VS2017 (15.9.28307.1033) found at: gyp ERR! find VS "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools" gyp ERR! find VS - found "Visual Studio C++ core features" gyp ERR! find VS - found VC++ toolset: v141 gyp ERR! find VS - missing any Windows SDK gyp ERR! find VS could not find a version of Visual Studio 2017 or newer to use gyp ERR! find VS looking for Visual Studio 2015 gyp ERR! find VS - not found gyp ERR! find VS not looking for VS2013 as it is only supported up to Node.js 8 gyp ERR! find VS gyp ERR! find VS ************************************************************** gyp ERR! find VS You need to install the latest version of Visual Studio gyp ERR! find VS including the "Desktop development with C++" workload. gyp ERR! find VS For more information consult the documentation at: gyp ERR! find VS https://github.com/nodejs/node-gyp#on-windows gyp ERR! find VS ************************************************************** gyp ERR! find VS gyp ERR! configure error gyp ERR! stack Error: Could not find any Visual Studio installation to use gyp ERR! stack at VisualStudioFinder.fail (C:\Users\killa\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:121:47) gyp ERR! stack at findVisualStudio2013 (C:\Users\killa\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:74:16) gyp ERR! stack at VisualStudioFinder.findVisualStudio2013 (C:\Users\killa\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:351:14) gyp ERR! stack at findVisualStudio2015 (C:\Users\killa\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:70:14) gyp ERR! stack at regSearchKeys (C:\Users\killa\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:372:16) gyp ERR! stack at regGetValue (C:\Users\killa\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\util.js:54:7) gyp ERR! stack at C:\Users\killa\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\util.js:33:16 gyp ERR! stack at ChildProcess.exithandler (child_process.js:301:5) gyp ERR! stack at ChildProcess.emit (events.js:198:13) gyp ERR! stack at maybeClose (internal/child_process.js:982:16) gyp ERR! System Windows_NT 10.0.18362 gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\killa\\AppData\\Roaming\\npm\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" gyp ERR! cwd C:\Users\killa\Desktop\SteamTest\node_modules\node-pty gyp ERR! node -v v10.16.0 gyp ERR! node-gyp -v v5.0.5 gyp ERR! not ok

Killa4 commented 4 years ago

After running npm config set msvs_version 2017 Seemed to fix it

jens1101 commented 4 years ago

Thanks, @Killa4 for letting me know about the fix. I personally couldn't reproduce this on my Windows machine, so this helps. I will update the Readme.