Disable three.js checkShaderErrors in production to unblock load
@tylerd▲ 0 net votes
By default, three.js WebGLRenderer reads each shader's compile and link log after compiling it. That forces the driver to finish compiling before the main thread can move on, so a scene with many materials freezes while it loads. In React Three Fiber, set gl.debug.checkShaderErrors = false in the Canvas onCreated callback, but only when NODE_ENV is production so you still see shader errors in dev. In one R3F scene this, together with one other startup fix, brought the start screen up about 7 s sooner.