Hello,
I saw this warning while running actions on GitHub
Node.js 16 actions are deprecated.
Indeed, Node.js 16 is deprecated for actions and they recommend moving to Node.js LTS 20 (GitHub Actions: Transitioning from Node 16 to Node 20 - GitHub Changelog)
Our plan is to transition all actions to run on Node 20 by Spring 2024
Shall we try to move to Node.js 20.11.0 (npm 10.2.4)?
Actually, we’re using Node 18, but I still opened a PR to upgrade to the latest version of GitHub Actions.
Totally up for upgrading to Node 20 for Gladys + GitHub Actions 
Thanks for the PRs, let me know when it’s ready for review!
Alright, for Node 20, we have a « slight » blockage 
After 2 days banging my head on endless Docker builds, I came across this issue NPM install stucks with node:20 · Issue #1946 · nodejs/docker-node · GitHub
From what I understand, you can’t use npm in the node-20 images for the linux/arm/v6, linux/arm/v7 platforms and that matches my endless build.
These platforms correspond to older versions of the Raspberry Pi (1, Zero / Zero W/WH and 2 Model A). Are we maintaining the build for these platforms?
Otherwise, a test image cicoub13/gladys:node-20 has been deployed on my RPI4 for a few days, nothing to report.
Gladys - Node 20 by cicoub13 · Pull Request #2039 · GladysAssistant/Gladys · GitHub
Gladys Gateway NOT TESTED - chore(node): Update to node 20 by cicoub13 · Pull Request #159 · GladysAssistant/gladys-gateway · GitHub
Gladys Documentation - docs: Update to node 20 by cicoub13 · Pull Request #256 · GladysAssistant/v4-website · GitHub
Thanks for the PRs and all the work done @cicoub13 
[quote=« cicoub13, post:4, topic:8691 »]
From what I understand, we can’t
No, it’s people from other open-source projects who are removing ARM v7 but it’s still not fixed. We can wait a bit 
Ok.
As long as it doesn’t have an impact on users (or development), we might as well stay on Node 18, because removing a platform would have a
For info, the bug is still present and also affects Node 22:
For your information, I had to drop support for arm/v6 when moving to DuckDB, because quite simply the Node.js image no longer supports it in its -slim Debian-based version.
I have the impression, however, that the problem with Node 20 and arm/v7 is still present…
If this continues, we’ll be forced to drop support for arm/v7; it may be a necessary evil because, after all, even Pi 3s are arm64 as far as I understand, so we won’t be losing any major platforms either.
Quick update on this topic!
We’re going to soon be two major versions behind Node.js, because Node 22 will move to LTS during the month.
I’ve decided to drop support for arm/v7, which I don’t recommend anymore anyway.
→ The mini-PCs I recommend are amd64
→ Raspberry Pis from the Pi 3 onward are arm64
In my view, we’re not losing any major platforms and this really allows us to move forward.
This will enable two things:
…)The PR is here:
Edit: A build now takes 42 minutes instead of 4h10 
Are the remaining 3 h only to build the armv7 version?!
It’s worse than that, builds are launched in parallel so the total time is the time of the longest build, i.e. 4h10 for ARMv7
Node 22 is now in LTS 
I tried to update locally, but it’s not that simple
On the frontend, impossible to start with Node 22:
63: 0x10226dc60 node::StartExecution(node::Environment*, char const*) [/Users/pierre-gillesleymarie/.volta/tools/image/node/22.11.0/bin/node]
64: 0x10226db80 node::StartExecution(node::Environment*, std::__1::function\u003cv8::MaybeLocal\u003cv8::Value\u003e (node::StartExecutionCallbackInfo const\u0026)\u003e) [/Users/pierre-gillesleymarie/.volta/tools/image/node/22.11.0/bin/node]
65: 0x1021d6460 node::LoadEnvironment(node::Environment*, std::__1::function\u003cv8::MaybeLocal\u003cv8::Value\u003e (node::StartExecutionCallbackInfo const\u0026)\u003e, std::__1::function\u003cvoid (node::Environment*, v8::Local\u003cv8::Value\u003e, v8::Local\u003cv8::Value\u003e)\u003e) [/Users/pierre-gillesleymarie/.volta/tools/image/node/22.11.0/bin/node]
66: 0x1022fdc98 node::NodeMainInstance::Run(node::ExitCode*, node::Environment*) [/Users/pierre-gillesleymarie/.volta/tools/image/node/22.11.0/bin/node]
67: 0x1022fda90 node::NodeMainInstance::Run() [/Users/pierre-gillesleymarie/.volta/tools/image/node/22.11.0/bin/node]
68: 0x10227159c node::Start(int, char**) [/Users/pierre-gillesleymarie/.volta/tools/image/node/22.11.0/bin/node]
69: 0x19d314274 start [/usr/lib/dyld]
----- JavaScript stack trace -----
1: /Users/pierre-gillesleymarie/code/gladys/front/node_modules/esm/esm.js:1:34535
2: /Users/pierre-gillesleymarie/code/gladys/front/node_modules/esm/esm.js:1:34176
3: /Users/pierre-gillesleymarie/code/gladys/front/node_modules/esm/esm.js:1:34506
4: /Users/pierre-gillesleymarie/code/gladys/front/node_modules/esm/esm.js:1:173374
5: /Users/pierre-gillesleymarie/code/gladys/front/node_modules/esm/esm.js:1:173420
6: /Users/pierre-gillesleymarie/code/gladys/front/node_modules/esm/esm.js:1:173521
7: /Users/pierre-gillesleymarie/code/gladys/front/node_modules/esm/esm.js:1:258942
8: /Users/pierre-gillesleymarie/code/gladys/front/node_modules/esm/esm.js:1:261569
9: e (/Users/pierre-gillesleymarie/code/gladys/front/node_modules/esm/esm.js:1:262673)
10: get (/Users/pierre-gillesleymarie/code/gladys/front/node_modules/esm/esm.js:1:262740)
After looking into it a bit, the issue is also present on Node 20:
The problem is that preact-cli is no longer maintained; apparently you need to switch to vite:
Apparently, there is a solution :
The PR:
I just ran a real test with a test Docker image, and it’s a success!
@contributors I just merged into master — please remember to update your environments
Oh that’s awesome, thanks!! I’ll be able to add modules to Node-RED that couldn’t be installed with Node 18 
@mutmut I think you’re confusing two things, here I’m talking about Gladys, not Node-RED!
For Node-RED, it’s discussed here:
