When we tried to update Chromium CI's version of node to v18.20.3, (https://chromium-review.googlesource.com/c/emscripten-releases/+/5503423/2, patchset 2) we found a strange case where the tests on the mac builder hung without any useful output.
I subsequently tried node v19, 20, and 22 (patchsets 6, 8, and 7 respectively. Node 19 displayed the same behavior, while the tests for 20 and 22 did not.
The current plan is just to revert #22010 for now, which would mean we'd still be distributing node 18 in emsdk, but default emscripten output wouldn't refuse to run on node 16. That seems fine until we figure out what's happening with node 18 or decide to just use a different node on chromium CI
When we tried to update Chromium CI's version of node to v18.20.3, (https://chromium-review.googlesource.com/c/emscripten-releases/+/5503423/2, patchset 2) we found a strange case where the tests on the mac builder hung without any useful output.
I subsequently tried node v19, 20, and 22 (patchsets 6, 8, and 7 respectively. Node 19 displayed the same behavior, while the tests for 20 and 22 did not.
The current plan is just to revert #22010 for now, which would mean we'd still be distributing node 18 in emsdk, but default emscripten output wouldn't refuse to run on node 16. That seems fine until we figure out what's happening with node 18 or decide to just use a different node on chromium CI