dashy icon indicating copy to clipboard operation
dashy copied to clipboard

[BUG] Unable to install Dashy on Node 18 LTS

Open InspecteurKepler opened this issue 2 years ago • 7 comments

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/[email protected] dependency is not up to date and can only be installed on Node 17 or lower.

Additional info

image

error @achrinza/[email protected]: 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

InspecteurKepler avatar Apr 07 '23 17:04 InspecteurKepler

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

liss-bot avatar Apr 07 '23 17:04 liss-bot

  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

saccohuo avatar May 05 '23 16:05 saccohuo

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.

darkone23 avatar May 12 '23 05:05 darkone23

+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...

vincele avatar May 13 '23 12:05 vincele

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

InspecteurKepler avatar Jun 04 '23 10:06 InspecteurKepler

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

strbean avatar Aug 29 '23 21:08 strbean

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

g0rbe avatar Oct 27 '23 23:10 g0rbe

@Lissy93 ⚠️ This should really have some priority, ALL Vercel build will fail after 15.06.24 which is in 4 months.-

Warning: Due to "engines": { "node": ">=16.0.0

CrazyWolf13 avatar Feb 21 '24 19:02 CrazyWolf13

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

CrazyWolf13 avatar Feb 24 '24 22:02 CrazyWolf13

Tested, it even works with Node 20.11.1 LTS 🚀

CrazyWolf13 avatar Feb 28 '24 15:02 CrazyWolf13

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

error @achrinza/[email protected]: 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.

kurimanju-dev avatar Apr 25 '24 08:04 kurimanju-dev

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

error @achrinza/[email protected]: 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'

CrazyWolf13 avatar Apr 25 '24 10:04 CrazyWolf13

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/[email protected]: 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/[email protected]: 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.

jordanbr20 avatar Jul 18 '24 15:07 jordanbr20