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

[BUG] Unable to install Dashy on Node 18 LTS #1159

Closed
4 of 5 tasks
DAMIOSKIDEV opened this issue Apr 7, 2023 · 13 comments
Closed
4 of 5 tasks

[BUG] Unable to install Dashy on Node 18 LTS #1159

DAMIOSKIDEV opened this issue Apr 7, 2023 · 13 comments
Assignees
Labels
🐛 Bug [ISSUE] Ticket describing something that isn't working

Comments

@DAMIOSKIDEV
Copy link

DAMIOSKIDEV commented Apr 7, 2023

Environment

Self-Hosted (Bare Metal)

System

Ubuntu 22.04.2 LTS x86_64

Version

2.1.1

Describe the problem

Impossible to install Dashy on the latest LTS version of NodeJS (18.18.0). The achrinza/node-ipc@9.2.2 dependency is not up to date and can only be installed on Node 17 or lower.

Additional info

image

error @achrinza/node-ipc@9.2.2: The engine "node" is incompatible with this module. Expected version "8 || 10 || 12 || 14 || 16 || 17". Got "18.15.0"
error Found incompatible module.

Please tick the boxes

@DAMIOSKIDEV DAMIOSKIDEV added the 🐛 Bug [ISSUE] Ticket describing something that isn't working label Apr 7, 2023
@liss-bot
Copy link
Collaborator

liss-bot commented Apr 7, 2023

If you're enjoying Dashy, consider dropping us a ⭐
🤖 I'm a bot, and this message was automated

@saccohuo
Copy link

saccohuo commented May 5, 2023

  1. go to package.json
  2. change node version from "node": ">16.0.0" to "node": "^16.3.0"
  3. redeploy with new git project

@liss-bot liss-bot added the 👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending label May 5, 2023
@darkone23
Copy link

Commented in pull#1178 - ran into this today - can't install on node 18 - works fine on 16.

Several libraries need updating to make it possible - not just node-ipc.

@liss-bot liss-bot removed the 👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending label May 13, 2023
@vincele
Copy link

vincele commented May 13, 2023

+1 I also have this problem today trying to deploy on debian 12 bookworm

EDIT: add more debian info

12 (bookworm): 18.13
11 (bullseye): 12.22

Looks like no debian version has suitable node to run dashy...

@liss-bot liss-bot added 👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending and removed 👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending labels May 13, 2023
@DAMIOSKIDEV
Copy link
Author

For those wondering how to solve this issue temporarily, use nvm and install version 16.13.0

@liss-bot liss-bot added the 👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending label Jun 4, 2023
@strbean
Copy link

strbean commented Aug 29, 2023

Node.js 16 goes into end-of-life status on 2023-09-11. Maybe support for version 18 should be a priority?

@liss-bot liss-bot removed the 👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending label Aug 30, 2023
@g0rbe
Copy link

g0rbe commented Oct 27, 2023

@Lissy93 Any update about this issue? NodeJS 16 is EOL

@liss-bot liss-bot added the 👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending label Oct 27, 2023
@CrazyWolf13

This comment was marked as outdated.

@CrazyWolf13
Copy link
Collaborator

✨ This will be fixed in 2.1.2, which will be released soon. 🎉

@liss-bot liss-bot removed the 👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending label Feb 27, 2024
@CrazyWolf13
Copy link
Collaborator

Tested, it even works with Node 20.11.1 LTS 🚀

@luigiistcrazy
Copy link

Still doesn't work for me. I still get this error:

error @achrinza/node-ipc@9.2.2: The engine "node" is incompatible with this module. Expected version "8 || 10 || 12 || 14 || 16 || 17". Got "18.19.0"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

@CrazyWolf13
Copy link
Collaborator

Still doesn't work for me. I still get this error:

error @achrinza/node-ipc@9.2.2: The engine "node" is incompatible with this module. Expected version "8 || 10 || 12 || 14 || 16 || 17". Got "18.19.0"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Did you run with ignore engines?

'yarn install --ignore-engines'

@jordanbr20
Copy link

jordanbr20 commented Jul 18, 2024

I agree, this does not seem to be fixed at this point.

Using version 18.20.4, and changing the package.json to "node": ">16.3.0" under engines, I still get this.

@achrinza/node-ipc@9.2.2: The engine "node" is incompatible with this module. Expected version "8 || 10 || 12 || 14 || 16 || 17". Got "18.20.4"

I had originally started with node version 20.15.1 with the package.json change as well but got this error.

error @achrinza/node-ipc@9.2.2: The engine "node" is incompatible with this module. Expected version "8 || 10 || 12 || 14 || 16 || 17". Got "20.15.1"

running yarn install --ignore-engines did seem to run the command but got the bellow when running yarn build

$ NODE_OPTIONS=--openssl-legacy-provider vue-cli-service build 'NODE_OPTIONS' is not recognized as an internal or external command, operable program or batch file. error Command failed with exit code 1.

Running npm i cross-env and modifying the package.json to "build": "cross-env NODE_OPTIONS=--openssl-legacy-provider vue-cli-service build",.

Doing the above, made it run further than before, but still errored out and failed to build.

Running yarn build --fix (as yarn suggested) still did not work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug [ISSUE] Ticket describing something that isn't working
Projects
Status: Done
Development

No branches or pull requests