On Thu, Jun 03, 2021 at 11:17:44AM +0200, Dirk Müller wrote:
Hi Adam,
Am Fr., 28. Mai 2021 um 13:42 Uhr schrieb Adam Majer <amajer@suse.de>:
PS. just out of curiosity, what is broken with nodejs16 that was working with 14 or older?
I don't think thats the right question - nodejs14 is LTS and supported upstream and imho should be available in tumbleweed because there are popular open source projects (not in tumbleweed) currently still requiring nodejs 14.
I personally started developing on one of them in the last few weeks and while I thought "nah, it can't be that hard to go with nodejs16", about two days later I just deleted the whole effort as I had tens of little issues here and there, and upstream was not willing to move to nodejs16 yet because not all dependencies were compatible with 16, or required a major version update that caused fallout in the project itself that is non-trivial to resolve.
I tried to build a couple of projects using npm, and while one mysteriously fails with node16 without any explanation another builds but fails to find its native libraries once started. Switching to node10 - the only other one available in Tumbleweed resolved both issues. So no, upstream projects are generally not ready to build with the latest and greates node. It is great to have it available to debug such issues but to actually use software that uses node the LTS vestions are needed. Thanks Michal