the general pattern here is to install headless-gl, install jsdom, and then patch any errors you see from three.js by adding jsdom globals until the errors stop.
#Serverside Node.js rendering
tight kite
i don't think anyone is maintaining complete documentation on how to do that, which would be hard because you need to keep track of which Web APIs are used by every feature of three.js.
Other big caveat here - new three.js versions will not support WebGL 1 much longer, and headless-gl only supports WebGL1, they never upgraded to WebGL 2.
I so would expect some gaps in serverside rendering until either there's a WebGL 2 implementation in node.js (unsure if this is planned), or until WebGPU is more stable in three.js and in serverside implementations.