robertsLando
commented
4 years ago The error is with puppeteer@5.0.0 but this node is using puppeteer 3.0.0. Uninstall puppeteer and install this node again
Closed antonag closed 4 years ago
robertsLando
commented
4 years ago The error is with puppeteer@5.0.0 but this node is using puppeteer 3.0.0. Uninstall puppeteer and install this node again
I can´t install, this is the log:
npm install node-red-contrib-whatsappbot --save
(node:8809) UnhandledPromiseRejectionWarning: /home/pi/.node-red/node_modules/@open-wa/wa-automate/node_modules/puppeteer/lib/cjs/install.js:134 catch { ^
SyntaxError: Unexpected token { at createScript (vm.js:80:10) at Object.runInThisContext (vm.js:139:10) at Module._compile (module.js:617:28) at Object.Module._extensions..js (module.js:664:10) at Module.load (module.js:566:32) at tryModuleLoad (module.js:506:12) at Function.Module._load (module.js:498:3) at Module.require (module.js:597:17) at require (internal/module.js:11:18) at download (/home/pi/.node-red/node_modules/@open-wa/wa-automate/node_modules/puppeteer/install.js:32:44) (node:8809) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1) (node:8809) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
ERR! sharp Use with glibc 2.24 requires manual installation of libvips >= 8.9.1 info sharp Attempting to build from source via node-gyp but this may fail due to the above error info sharp Please see https://sharp.pixelplumbing.com/install for required dependencies make: se entra en el directorio '/home/pi/.node-red/node_modules/sharp/build' TOUCH Release/obj.target/libvips-cpp.stamp CC(target) Release/obj.target/nothing/node_modules/node-addon-api/nothing.o AR(target) Release/obj.target/node_modules/node-addon-api/nothing.a COPY Release/nothing.a CXX(target) Release/obj.target/sharp/src/common.o ../src/common.cc:23:22: fatal error: vips/vips8: No existe el fichero o el directorio
include <vips/vips8>
compilation terminated. sharp.target.mk:128: fallo en las instrucciones para el objetivo 'Release/obj.target/sharp/src/common.o' make: *** [Release/obj.target/sharp/src/common.o] Error 1 make: se sale del directorio '/home/pi/.node-red/node_modules/sharp/build' gyp ERR! build error gyp ERR! stack Error:
makefailed with exit code: 2 gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:262:23) gyp ERR! stack at emitTwo (events.js:126:13) gyp ERR! stack at ChildProcess.emit (events.js:214:7) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12) gyp ERR! System Linux 4.19.27-v7+ gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" gyp ERR! cwd /home/pi/.node-red/node_modules/sharp gyp ERR! node -v v8.12.0 gyp ERR! node-gyp -v v3.8.0 gyp ERR! not ok npm WARN ws@7.3.1 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer dependencies yourself. npm WARN ws@7.3.1 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself. npm WARN ws@7.3.1 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer dependencies yourself. npm WARN ws@7.3.1 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself. npm WARN node-red-project@0.0.1 No repository field. npm WARN node-red-project@0.0.1 No license field.npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! sharp@0.25.4 install:
(node install/libvips && node install/dll-copy && prebuild-install --runtime=napi) || (node-gyp rebuild && node install/dll-copy)npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the sharp@0.25.4 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/pi/.npm/_logs/2020-07-12T12_29_08_087Z-debug.log