Bug 23884 - Running yarn to start bulding projects like signal-desktop and wire-desktop gives " error signal-desktop@1.18.0-beta.7: The engine "node" is incompatible with this module. Expected version "^8.9.3". Got "6.10.3" "
Summary: Running yarn to start bulding projects like signal-desktop and wire-desktop g...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Joseph Wang
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-22 11:29 CET by Kristoffer Grundström
Modified: 2020-04-06 11:33 CEST (History)
3 users (show)

See Also:
Source RPM: nodejs
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Kristoffer Grundström 2018-11-22 11:29:33 CET 
Description of problem: Please backport the nodejs version 10.13.0 from Cauldron to Mageia 6 as I can't get the yarn command to work with either of the mentioned projects due to incompability as the current version in Mageia 6 is to old.

Version-Release number of selected component (if applicable): 10.13.0

How reproducible: All the time.

Steps to Reproduce:
1. Run git clone https://github.com/signalapp/Signal-Desktop.git 
2. cd to Signal-Desktop
3. Run yarn.
4. The command fails with this line: error signal-desktop@1.18.0-beta.7: The engine "node" is incompatible with this module. Expected version "^8.9.3". Got "6.10.3"
Kristoffer Grundström 2018-11-22 11:29:44 CET

CC: (none) => hamnisdude

Comment 1 Marja Van Waes 2018-11-24 11:19:52 CET 
Assigning to the registered nodejs maintainer.

Assignee: bugsquad => joequant
CC: (none) => marja11

Comment 2 Kristoffer Grundström 2019-06-30 02:39:15 CEST 
nodejs has been updated to a LTS version. Someone willing to push an update to Cauldron at least?
Comment 3 Lewis Smith 2020-04-06 10:41:13 CEST 
Is this bug still valid? Our current version for M7 is nodejs-10.15.3-8.mga7

CC: (none) => lewyssmith

Comment 4 Kristoffer Grundström 2020-04-06 11:33:16 CEST 
This problem seems to be solved. At least in Cauldron.

Changing to RESOLVED FIXED.

Should anyone feel that this is not valid, feel free to reopen with an additional comment.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.