Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
- npm ERR! code 1
- npm ERR! path C:\Users\maxmustermann\Desktop\robotjs\node_modules\robotjs
- npm ERR! command failed
- npm ERR! command C:\Windows\system32\cmd.exe /d /s /c prebuild-install || node-gyp rebuild
- npm ERR! gyp info it worked if it ends with ok
- npm ERR! gyp info using node-gyp@9.0.0
- npm ERR! gyp info using node@18.3.0 | win32 | x64
- npm ERR! gyp info find Python using Python version 3.10.5 found at "C:\Users\maxmustermann\AppData\Local\Microsoft\WindowsApps\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\python.exe"
- npm ERR! gyp ERR! find VS
- npm ERR! gyp ERR! find VS msvs_version not set from command line or npm config
- npm ERR! gyp ERR! find VS VCINSTALLDIR not set, not running in VS Command Prompt
- npm ERR! gyp ERR! find VS checking VS2022 (17.2.32602.215) found at:
- npm ERR! gyp ERR! find VS "C:\Program Files\Microsoft Visual Studio\2022\Community"
- npm ERR! gyp ERR! find VS - found "Visual Studio C++ core features"
- npm ERR! gyp ERR! find VS - missing any VC++ toolset
- npm ERR! gyp ERR! find VS checking VS2019 (16.11.32602.291) found at:
- npm ERR! gyp ERR! find VS "C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools"
- npm ERR! gyp ERR! find VS - found "Visual Studio C++ core features"
- npm ERR! gyp ERR! find VS - missing any VC++ toolset
- npm ERR! gyp ERR! find VS could not find a version of Visual Studio 2017 or newer to use
- npm ERR! gyp ERR! find VS looking for Visual Studio 2015
- npm ERR! gyp ERR! find VS - not found
- npm ERR! gyp ERR! find VS not looking for VS2013 as it is only supported up to Node.js 8
- npm ERR! gyp ERR! find VS
- npm ERR! gyp ERR! find VS **************************************************************
- npm ERR! gyp ERR! find VS You need to install the latest version of Visual Studio
- npm ERR! gyp ERR! find VS including the "Desktop development with C++" workload.
- npm ERR! gyp ERR! find VS For more information consult the documentation at:
- npm ERR! gyp ERR! find VS https://github.com/nodejs/node-gyp#on-windows
- npm ERR! gyp ERR! find VS **************************************************************
- npm ERR! gyp ERR! find VS
- npm ERR! gyp ERR! configure error
- npm ERR! gyp ERR! stack Error: Could not find any Visual Studio installation to use
- npm ERR! gyp ERR! stack at VisualStudioFinder.fail (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:122:47)
- npm ERR! gyp ERR! stack at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:75:16
- npm ERR! gyp ERR! stack at VisualStudioFinder.findVisualStudio2013 (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:363:14)
- npm ERR! gyp ERR! stack at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:71:14
- npm ERR! gyp ERR! stack at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:384:16
- npm ERR! gyp ERR! stack at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\util.js:54:7
- npm ERR! gyp ERR! stack at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\util.js:33:16
- npm ERR! gyp ERR! stack at ChildProcess.exithandler (node:child_process:395:5)
- npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:527:28)
- npm ERR! gyp ERR! stack at maybeClose (node:internal/child_process:1090:16)
- npm ERR! gyp ERR! System Windows_NT 10.0.19044
- npm ERR! gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
- npm ERR! gyp ERR! cwd C:\Users\maxmustermann\Desktop\robotjs\node_modules\robotjs
- npm ERR! gyp ERR! node -v v18.3.0
- npm ERR! gyp ERR! node-gyp -v v9.0.0
- npm ERR! gyp ERR! not ok
- npm ERR! A complete log of this run can be found in:
- npm ERR! C:\Users\maxmustermann\AppData\Local\npm-cache\_logs\2022-06-16T13_03_34_422Z-debug-0.log
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement