Solution to the problem of version number mismatch in running electron and robot JS
Running found that the error version number does not match, to reduce the node version number, the result found that it is not the version number problem
<project>/node_modules/robotjs/build/Release/robotjs.node' was compiled against a different Node.js version using
NODE_MODULE_VERSION 57.
This version of Node.js requires NODE_MODULE_VERSION 54.
Please try re-compiling or re-installing the module (for instance, using npm rebuild or npm install).
After one operation, the node gyp construction error was reported again
node-expat.3.18 install /usr/local/lib/nodejs/node-v14.0.0-linux-x64/lib/node_modules/rnv/node_modules/node-expat node-gyp rebuild
gyp ERR! clean error gyp ERR! stack Error: EACCES: permission denied, rmdir 'build' gyp ERR! System Linux 5.3.0-51-generic gyp ERR! command "/usr/local/lib/nodejs/node-v14.0.0-linux-x64/bin/node" "/usr/local/lib/nodejs/node-v14.0.0-linux-x64/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" gyp ERR! cwd /usr/local/lib/nodejs/node-v14.0.0-linux-x64/lib/node_modules/rnv/node_modules/node-expat gyp ERR! node -v v14.0.0 gyp ERR! node-gyp -v v5.1.0 gyp ERR! not ok npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected]^1.2.7 (node_modules/rnv/node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN rnv.29.0 requires a peer of now.3.0 but none is installed. You must install peer dependencies yourself.
npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! node-expat.3.18 install: node-gyp rebuild npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the node-expat.3.18 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! /home/abhishek/.npm/_logs/2020-05-10T08_21_14_099Z-debug.log
Solution: to delete the project again and execute the following command again can solve most of the problems
target is the electron version number
By printing console.info ( process.versions ）;
view the corresponding relationship between
node and ABI: see
cnpm rebuild --runtime=electron --target=8.5.5 --disturl=https://atom.io/download/atom-shell --abi=72
Read More:
- (Caused by SSLError(SSLError(1, ‘[SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1123)‘)))
- Error: the version of ZABBIX database does not match the current requirements
- NPM and Node.js Version incompatibility
- An error is reported when the electron Vue Vue component introduces the electron
- Error: ‘default’ is not exported by node_ modules/qs/lib/ index.js
- Mmdetection reports an error when running its own coco dataset. Does not match the length of \ ` classes \ ` 80) in cocodataset
- After node.js is installed, use the instruction node version in vscode to show that it is not an external or internal instruction. The solution is as follows:
- Problems in compiling and using node FFI under electron
- urllib3 (1.26.4) or chardet (4.0.0) doesn‘t match a supported version!
- Item exception: failed to get the required ADT version number from the SDK
- Points for attention in setting up robot framework + Python 3.7.0 environment
- Solution to electron error “cannot find module app”
- [Solved] This dependency was not found: * core-js/modules/es.error.cause.js in ./node_modules/@babel
- ERROR in static/js/app.xxxxxxx.js from UglifyJs Unexpected token: operator (＞)
- JS error: require is not defined
- Error in pom.xml dependency version number in idea
- Caused by: java.sql.SQLException: Parameter index out of range (1 ＞ number of parameters, which is 0
- A method of collecting JS dynamic content by PHP
- After NPM run dev is running, the browser does not respond and reports an error in. / ~ / Babel loader / lib! / ~ / Vue loader / lib/ selector.js?type=script&in
- Shell script running error bash: JPS: command not found