PDA

View Full Version : [OPEN] stc 2.0.2 windows x64 fail to start



dngpng
28 Mar 2017, 12:48 AM
Here is the error output



C:\stc-2.0.2-win-x64>stc
C:\stc-2.0.2-win-x64\node_modules\orion-core\node_modules\bindings\bindings.js:96
throw err
^


Error: Could not locate the bindings file. Tried:
→ C:\stc-2.0.2-win-x64\node_modules\orion-core\node_modules\ref\compiled\electron\51\win32\x64\binding.node
→ C:\stc-2.0.2-win-x64\node_modules\orion-core\node_modules\ref\compiled\node\51\win32\x64\binding.node
→ C:\stc-2.0.2-win-x64\node_modules\orion-core\node_modules\ref\build\binding.node
→ C:\stc-2.0.2-win-x64\node_modules\orion-core\node_modules\ref\build\Debug\binding.node
→ C:\stc-2.0.2-win-x64\node_modules\orion-core\node_modules\ref\build\Release\binding.node
→ C:\stc-2.0.2-win-x64\node_modules\orion-core\node_modules\ref\out\Debug\binding.node
→ C:\stc-2.0.2-win-x64\node_modules\orion-core\node_modules\ref\Debug\binding.node
→ C:\stc-2.0.2-win-x64\node_modules\orion-core\node_modules\ref\out\Release\binding.node
→ C:\stc-2.0.2-win-x64\node_modules\orion-core\node_modules\ref\Release\binding.node
→ C:\stc-2.0.2-win-x64\node_modules\orion-core\node_modules\ref\build\default\binding.node
→ C:\stc-2.0.2-win-x64\node_modules\orion-core\node_modules\ref\compiled\7.5.0\win32\x64\binding.node
at bindings (C:\stc-2.0.2-win-x64\node_modules\orion-core\node_modules\bindings\bindings.js:93:9)
at Object.<anonymous> (C:\stc-2.0.2-win-x64\node_modules\orion-core\node_modules\ref\lib\ref.js:5:47)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
at Module.require (module.js:498:17)
at require (internal/module.js:20:19)
at Object.<anonymous> (C:\stc-2.0.2-win-x64\node_modules\orion-core\node_modules\ffi\lib\ffi.js:6:11)

craigcomstock
29 Mar 2017, 7:41 AM
Sorry. At this time you must use node 6.x. I suspect you are using 7.x based on the number 51 in that error log. That indicates the Node ABI (application binary interface) version of node.

I would suggest either downgrading node or running something like nvm (node version manager) to select a different node version when you run stc.

We will be upgrading our binary modules in a future release.

zwikske
30 May 2017, 2:00 AM
Is this still true that you need Node 6? Because the documentation says you need Node 4.2.1 or newer... Even for STC 2.1.0. See: https://docs.sencha.com/sencha_test/2.1.0/guides/sencha_test_installation.html#sencha_test_installation_-_installing_stc

Otherwise please update the documentation...

I'm getting a similar issue on a Windows Server 2008 R2 machine that can't install anything higher than Node 4.x because of dropped support by Node. My ABI level is 46.

craigcomstock
30 May 2017, 7:52 AM
I will get the docs updated. STC 2.1.0 should work fine with node 7.

craigcomstock
29 Jun 2017, 5:19 AM
Yes, tracking node versions is a bit challenging since we rely on some native modules which are tied to specific major versions. Our next release may resolve this issue by STC not having a dependency on node at all. For now we support Node ABI 48 (6.x) and 51 (7.x) but nothing older or newer.