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] Dashy will not compile no matter which version of NodeJS I have. #1697

Open
5 tasks done
hackdefendr opened this issue Sep 22, 2024 · 4 comments
Open
5 tasks done
Assignees
Labels
👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending 🐛 Bug [ISSUE] Ticket describing something that isn't working

Comments

@hackdefendr
Copy link

Environment

Self-Hosted (Bare Metal)

System

Debian 12 Arm64 host, Debian 12 Arm64 VM, NodeJS 17, 18, 20, LTS

Version

git

Describe the problem

I am attempting to run yarn and no matter which version of NodeJS I have active globally the yarn process crashes as shown below.

With LTS:
error @achrinza/[email protected]: The engine "node" is incompatible with this module. Expected version "8 || 10 || 12 || 14 || 16 || 17". Got "20.17.0" error Found incompatible module.

With latest NodeJS 18:
error @achrinza/[email protected]: The engine "node" is incompatible with this module. Expected version "8 || 10 || 12 || 14 || 16 || 17". Got "18.20.4" error Found incompatible module.

With latest NodeJS 17:
error [email protected]: The engine "node" is incompatible with this module. Expected version ">=18". Got "17.9.1" error Found incompatible module.

Is there a specific version I should use to get past this?

Additional info

I had this all running under Docker, but wanted to explore running this on a bare metal or VM so I can develop widgets n stuff and also to run this in multi-user mode a bit easier. This version of Dashy was pulled this morning from Git.

Please tick the boxes

@hackdefendr hackdefendr added the 🐛 Bug [ISSUE] Ticket describing something that isn't working label Sep 22, 2024
@radek-dev
Copy link

radek-dev commented Sep 22, 2024

The same here. I am trying on Ubuntu 22.04.5 LTC now. I tried on Debian 11, 12. Both on Intel chipset. I tried many version of Node too.
Anyway, I was not able to get around this reported error in decencies.

Git tag for this is 3.1.1

@liss-bot liss-bot added the 👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending label Sep 22, 2024
@radek-dev
Copy link

radek-dev commented Sep 22, 2024

So, checking about the previous tag in git fixes the issue for me.
git checkout 3.0.1
This is not the actual fixed though.

@hackdefendr
Copy link
Author

I stumbled across these steps in the node-ipc issue for the same error.

$ yarn cache clean
yarn cache v1.22.22
success Cleared cache.
Done in 4.39s
$ yarn set version stable
➤ YN0000: You don't seem to have Corepack enabled; we'll have to rely on yarnPath instead
➤ YN0000: Downloading https://repo.yarnpkg.com/4.5.0/packages/yarnpkg-cli/bin/yarn.js
➤ YN0000: Saving the new release in .yarn/releases/yarn-4.5.0.cjs
➤ YN0000: Done with warnings in 0s 252ms

Then it completes the process.

$ yarn
➤ YN0000: · Yarn 4.5.0
➤ YN0000: ┌ Resolution step
➤ YN0085: │ + @babel/core@npm:7.25.2, @babel/preset-env@npm:7.25.4, @formschema/native@npm:2.0.0-beta.7, @sentry/tracing@npm:7.119.0, @sentry/vue@npm:7.119.0, @vue/cli-plugin-babel@npm:4.5.19, @vue/cli-plugin-eslint@npm:4.5.19, and 1509 more.
➤ YN0000: └ Completed in 20s 959ms
➤ YN0000: ┌ Post-resolution validation
➤ YN0002: │ dashy@workspace:. doesn't provide eslint-plugin-import (p4c5f1), requested by eslint-config-airbnb.
➤ YN0002: │ dashy@workspace:. doesn't provide eslint-plugin-jsx-a11y (pc0bb5), requested by eslint-config-airbnb.
➤ YN0002: │ dashy@workspace:. doesn't provide eslint-plugin-react (p7cf34), requested by eslint-config-airbnb.
➤ YN0002: │ dashy@workspace:. doesn't provide eslint-plugin-react-hooks (pf8e9b), requested by eslint-config-airbnb.
➤ YN0002: │ dashy@workspace:. doesn't provide webpack (p4b6a3), requested by copy-webpack-plugin and other dependencies.
➤ YN0086: │ Some peer dependencies are incorrectly met by your project; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code.
➤ YN0086: │ Some peer dependencies are incorrectly met by dependencies; run yarn explain peer-requirements for details.
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
➤ YN0013: │ 1514 packages were added to the project (+ 317.9 MiB).
➤ YN0000: └ Completed in 8s 874ms
➤ YN0000: ┌ Link step
➤ YN0007: │ yorkie@npm:2.0.0 must be built because it never has been before or the last one failed
➤ YN0007: │ ejs@npm:2.7.4 must be built because it never has been before or the last one failed
➤ YN0007: │ core-js@npm:3.38.1 must be built because it never has been before or the last one failed
➤ YN0007: │ core-js@npm:2.6.12 must be built because it never has been before or the last one failed
➤ YN0000: └ Completed in 10s 348ms
➤ YN0000: · Done with warnings in 40s 529ms

Hope this helps!

@liss-bot liss-bot removed the 👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending label Sep 23, 2024
@radek-chramosil
Copy link

This looks good. I haven't thought about doing this.

@liss-bot liss-bot added the 👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending label Sep 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending 🐛 Bug [ISSUE] Ticket describing something that isn't working
Projects
Status: Awaiting Triage
Development

No branches or pull requests

5 participants