You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 5, 2019. It is now read-only.
Since node-v8-clone is compiled through node-gyp it may be installed on Windows only if both Microsoft Visual Studio C++ 2013 and Python are installed.
It forces any project that depends on node-v8-clone to depend on MSVC++ 2013. But not only them, projects which depend on these projects will transitively depend on MSVC++ 2013 (example: lookfirst/gulp-helpers).
PS C:\work\polygon> npm install node-v8-clone
\
> node-v8-clone@0.6.2 install C:\work\polygon\node_modules\node-v8-clone
> node-gyp rebuild
C:\work\polygon\node_modules\node-v8-clone>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node rebuild )
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
MSBUILD : error MSB3428: Could not load the Visual C++ component "VCBuild.exe". To fix this, 1) install the .NET Framework 2.0 SDK, 2) install Microsoft Visual Studio 2005 or 3) add the location of the component to the system path if it is installed elsewhere. [C:\work\polygon\node_modules\node-v8-clone\build\binding.sln]
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:269:23)
gyp ERR! stack at ChildProcess.emit (events.js:110:17)
gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:1074:12)
gyp ERR! System Windows_NT 6.1.7601
gyp ERR! command "node" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\work\polygon\node_modules\node-v8-clone
gyp ERR! node -v v0.12.7
gyp ERR! node-gyp -v v2.0.1
gyp ERR! not ok
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "node-v8-clone"
npm ERR! node v0.12.7
npm ERR! npm v2.11.3
npm ERR! code ELIFECYCLE
npm ERR! node-v8-clone@0.6.2 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-v8-clone@0.6.2 install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the node-v8-clone package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls node-v8-clone
npm ERR! There is likely additional logging output above.
The text was updated successfully, but these errors were encountered:
Since node-v8-clone is compiled through node-gyp it may be installed on Windows only if both Microsoft Visual Studio C++ 2013 and Python are installed.
It forces any project that depends on node-v8-clone to depend on MSVC++ 2013. But not only them, projects which depend on these projects will transitively depend on MSVC++ 2013 (example: lookfirst/gulp-helpers).
To avoid it, could you distribute pre-compiled binaries through something like mapbox/node-pre-gyp like node-inspector/v8-debug and node-inspector/v8-profiler do.
Leaving here npm output to land Googe searches:
The text was updated successfully, but these errors were encountered: