O
O
OVK20152016-02-02 16:33:06
Node.js
OVK2015, 2016-02-02 16:33:06

NODE.JS and Module version mismatch. How to overcome?

Good afternoon!
There is such a module: https://www.npmjs.com/package/robotjs
There is node version: v4.2.4
Node works under WinXP SP3 . (don't ask why... so far it's the only way)
We managed to establish experimentally that it's possible to build robotJS normally under WinXP only for Node version 1.8.4.
The next version of node(2.0.0) is based on version 4.2.77.18 of the v8 engine.
Which, as I understand it, requires Visual C ++ 2013 for assembly.
When launched under node v4.2.4: a project with a module built for version 1.8.4, accordingly issues:
module.js:460
return process.dlopen(module, path. _makeLong(filename));
^
Error: Module version mismatch. Expected 46, got 42.
at Error (native)
at Object.Module._extensions..node (module.js:460:18)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:313:12 )
at Module.require (module.js:366:17)
at require (module.js:385:17)
at Object. (d:\NodeWorkBench\TestApp\node_modules\robotjs\index.js:1:80)
at Module._compile (module.js:435:26)
at Object.Module._extensions..js (module.js:442:10 )
at Module.load (module.js:356:32)
Actually questions:
1. Is it possible to somehow make friends with the current version of node?
2. Is there any VisualStudio alternative for building native node modules under WinXP?
3. Is there any alternative to robotJS itself?

Answer the question

In order to leave comments, you need to log in

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question