Replies: 5 comments
-
The 3.0 betas are using 18, and going forward it will be easier for us to update the version gradually across the modules. Some reading on the module developer side https://github.com/bitfocus/companion-module-base/wiki/Updating-nodejs |
Beta Was this translation helpful? Give feedback.
-
Thanks for the quick response! Is there ETA for getting 3.0 out? I see it is currently being worked on in https://github.com/orgs/bitfocus/projects/2 but cannot find any information about a planned release (or even a beta). |
Beta Was this translation helpful? Give feedback.
-
There isnt currently an ETA, but it is something I am thinking needs to be chased. |
Beta Was this translation helpful? Give feedback.
-
@Julusian: You know what (typically) does wonders to encourage module / dependent developers to migrate their code to non-backwards compatible updates? Giving them a deadline for when you will break their sh*t. :) |
Beta Was this translation helpful? Give feedback.
-
@DanielBaulig yeah, but its going to be the users who suffer and its a bad look for the project and a release that will bring a lot more stability if too many modules dont work. Nothing has been agreed for certain, but it has been suggested to hopefully have an RC out in mid april. |
Beta Was this translation helpful? Give feedback.
-
Companion currently requires NodeJS
>=14.18 <15
, which according to the endoflife.date information about NodeJS is out of Active Support since 2021-10-19 (but getting security support until 2023-04-30). Even NodeJS 16 is out of active Support since 2022-10-18.Are you planning to update Companion to be compatible to more recent NodeJS versions (preferrably 18+)?
Beta Was this translation helpful? Give feedback.
All reactions