-
Notifications
You must be signed in to change notification settings - Fork 51
Open
Description
Hello. I'm making a Discord bot, and I want to use win32ole to emulate ActiveXObject. But I can't install it locally, cuz of this error:
win32ole@0.1.3 install C:\Users\Professional\Documents\GitHub\alpha-cc\node_modules\win32ole
> node-gyp rebuild
C:\Users\Professional\Documents\GitHub\alpha-cc\node_modules\win32ole>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
C:\Users\Professional\Documents\GitHub\alpha-cc\node_modules\win32ole\build\node_win32ole.vcxproj(20,3): error MSB4019:
The imported project "C:\Microsoft.Cpp.Default.props" was not found. Confirm that the path in the <Import> declaration
is correct, and that the file exists on disk.
gyp ERR! build error
gyp ERR! stack Error: `C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe` failed with exit code: 1
gyp ERR! stack at ChildProcess.onExit (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:262:23)
gyp ERR! stack at ChildProcess.emit (events.js:198:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
gyp ERR! System Windows_NT 10.0.18362
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"
gyp ERR! cwd C:\Users\Professional\Documents\GitHub\alpha-cc\node_modules\win32ole
gyp ERR! node -v v10.16.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! win32ole@0.1.3 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the win32ole@0.1.3 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Professional\AppData\Roaming\npm-cache\_logs\2019-10-15T16_19_49_663Z-debug.log
How to solve this? Please help.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels