Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot install dependencies #91

Closed
Citrullin opened this issue Sep 23, 2020 · 6 comments
Closed

Cannot install dependencies #91

Citrullin opened this issue Sep 23, 2020 · 6 comments

Comments

@Citrullin
Copy link

Citrullin commented Sep 23, 2020

When executing npm install I get the following error.

npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated @hapi/joi@15.1.1: joi is leaving the @hapi organization and moving back to 'joi' (https://github.com/sideway/joi/issues/2411)
npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated webdriverio@4.14.4: outdated version, please use @next
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated @hapi/bourne@1.3.2: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated @hapi/topo@3.1.6: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated @hapi/hoek@8.5.1: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated @hapi/address@2.1.4: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.

> node-aead-crypto@2.2.0 preinstall /home/citrullin/git/wade/node_modules/node-aead-crypto
> node lib/preinstall.js

node-aead-crypto not needed on this system, since all ciphers are natively supported
npm WARN notsup Unsupported engine for node-aead-crypto@2.2.0: wanted: {"node":">4 <10"} (current: {"node":"12.18.3","npm":"6.14.6"})
npm WARN notsup Not compatible with your version of node/npm: node-aead-crypto@2.2.0
npm WARN notsup Unsupported engine for watchpack-chokidar2@2.0.0: wanted: {"node":"<8.10.0"} (current: {"node":"12.18.3","npm":"6.14.6"})
npm WARN notsup Not compatible with your version of node/npm: watchpack-chokidar2@2.0.0
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/watchpack-chokidar2/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/fork-ts-checker-webpack-plugin/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/webpack-dev-server/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-aead-crypto@2.2.0 preinstall: `node lib/preinstall.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the node-aead-crypto@2.2.0 preinstall 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/citrullin/.npm/_logs/2020-09-23T15_08_12_671Z-debug.log
> node --version
v12.18.3
> npm --version
6.14.6
> lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 19.10
Release:	19.10
Codename:	eoan

on commit 82caa3d4a9da5fa6469950acb0b6b8f86a4ad0c7

@egekorkan
Copy link
Member

Could you try to force install node-aead-crypto ? We have documented it here: https://github.com/tum-esi/wade#errors-and-known-problems and also at node-wot eclipse-thingweb/node-wot#136

If this is indeed the problem, I will push this troubleshoot somewhere more prominent :)

@Citrullin
Copy link
Author

Citrullin commented Sep 23, 2020

Could you try to force install node-aead-crypto ? We have documented it here: https://github.com/tum-esi/wade#errors-and-known-problems and also at node-wot eclipse/thingweb.node-wot#136

If this is indeed the problem, I will push this troubleshoot somewhere more prominent :)

Maybe at some point it makes sense to update all these packages. The warning are quite concerning. Especially when we talk about Electron. Looks like there is a native API for these kind of purposes in node these days.
"Note: This module is not necessary on NodeJS 10+ because you can now provide the authTagLength"

/e: Yep, as I guessed. Quite concerning.

gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack     at ChildProcess.emit (events.js:315:20)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
gyp ERR! System Linux 5.3.0-22-generic
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/citrullin/git/wade/node_modules/node-aead-crypto
gyp ERR! node -v v12.18.3
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok 
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm notice created a lockfile as package-lock.json. You should commit this file.
+ node-aead-crypto@2.2.0
added 32 packages from 39 contributors and audited 2089 packages in 20.689s

54 packages are looking for funding
  run `npm fund` for details

found 3 vulnerabilities (1 low, 1 moderate, 1 high)
  run `npm audit fix` to fix them, or `npm audit` for details

And also

> npm install

> w-ade@0.1.0 postinstall /home/citrullin/git/wade
> electron-builder install-app-deps

sh: 1: electron-builder: not found
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! w-ade@0.1.0 postinstall: `electron-builder install-app-deps`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the w-ade@0.1.0 postinstall 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/citrullin/.npm/_logs/2020-09-23T18_36_56_392Z-debug.log

Of course I am then not able to build it:

npm run electron:build

> w-ade@0.1.0 electron:build /home/citrullin/git/wade
> vue-cli-service electron:build

sh: 1: vue-cli-service: not found
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! w-ade@0.1.0 electron:build: `vue-cli-service electron:build`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the w-ade@0.1.0 electron:build 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/citrullin/.npm/_logs/2020-09-23T18_38_10_241Z-debug.log

@egekorkan
Copy link
Member

I have tried to understand what is going on. Some possible solutions:

  • Do you have node-gyp installed?
  • Can you try to install electron-builder? This should not be necessary though

Until I understand how to fix it, you can use the following AppImage
https://we.tl/t-Fq3Hf780Yk

Not the most professional way to share binary files probably :)

@Citrullin
Copy link
Author

I have tried to understand what is going on. Some possible solutions:

* Do you have node-gyp installed?

* Can you try to install electron-builder? This should not be necessary though

Until I understand how to fix it, you can use the following AppImage
https://we.tl/t-Fq3Hf780Yk

Not the most professional way to share binary files probably :)

Probably not ^^
I guess you are also available at the PlugFest. Couldn't join yesterday, but I will be in the call today. So maybe a good opportunity to figure it out.

@egekorkan
Copy link
Member

Yes I will be there :)

@egekorkan
Copy link
Member

So this is fixed via #95 . @Citrullin you can try again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants